Micro Focus PPM (formerly HPE PPM) is a comprehensive project and portfolio management tool that helps PMOs in large organizations prioritize and track their IT investments.
This section describes the basic steps needed to prepare your Micro Focus PPM instance for use with Viz.
We recommend that you create a new user within your external tool, to be used only for Viz. This is the user information you will enter when setting up your tool connection within Planview Viz. By creating a new user, you will ensure that the correct permissions are granted.
In general, your user account should have sufficient permissions to read artifacts in your tool.
Your user should have a secure password or token. Please be aware that Viz will not allow you to save a tool connection utilizing a weak password/token, such as 'tasktop.'
Before creating a connection to the Micro Focus PPM tool, a user with the necessary permissions must be created if one does not exist already. Follow the steps below to create a user with the necessary permissions for use with the connector:
Ensure the user is assigned a new or pre-existing Security Group that has the following Access Grants:
Project Mgmt: View Projects
For the Micro Focus PPM connector to function properly, the user must have the following permissions:
Requests:
Project Mgmt: View Projects
Tasks:
Standard Authentication
Required Fields:
Supported Work Item Type |
Applicable Repository Versions |
Unique URL? |
---|---|---|
Task |
Any supported repository version: |
Yes |
Containers that can be modeled as Flow Items |
Applicable Repository Versions |
Unique URL? |
---|---|---|
N/A |
|
|
Containers used to define which artifacts are included in an Artifact Set |
|
|
Projects |
Any supported repository version: |
N/A |
Planview Viz supports configuring rule-based modeling (i.e., conditional modeling) using the field types shown below.
Note: If one field of a given type is supported, others that are also that type in theory should also work. However, sometimes there are instances in which this is not the case due to the repository. So, while we can claim support for fields at the type level, there is a chance that some specific fields of a given type will not function properly.
Standard Field Type |
How is field type referenced in the repository? |
Sample Repository Fields Supported |
Particular Repository Fields NOT Supported |
---|---|---|---|
String |
|
Name, Description, Constraint Type (Read Only), Activity (Read Only), Assigned Role (Read Only), Transition Id (Read Only), Transition Label (Read Only) |
|
Single Select |
|
Search Type, Project (Read Only), Search Project, Type (Read Only), Status (Read Only), Assigned Roles (can be synchronized bidirectionally on Task artifacts), SQL Based Single Select (Read Only) |
|
Multi Select |
|
|
|
Boolean |
|
Is Milestone (Read Only), Is Major Milestone (Read Only), Milestones Auto Complete, Closed (Read Only) |
|