Planview PPM Pro
Overview
Planview PPM Pro provides the ability to collect, prioritize and execute projects while enabling teams to focus their resources on work that provides the most value. Project managers, program managers, PMO leaders, resource managers and CIOs can use Planview PPM Pro to gain top-down visibility into their project portfolio and align work with business goals, while facilitating governance and empowering every team to work collaboratively and effectively.
Connector Setup Details
This section describes the basic steps needed to prepare your Planview PPM Pro instance for use with Viz.
Minimal User Permissions & Viz User
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.'
Learn how to create a custom user in Planview PPM Pro here.
Connecting to the Planview PPM Pro Repository
Standard Authentication
Required Fields:
-
URL
-
Example Format: https://example.ppmpro.com
-
-
Username
-
Password
Supported Artifacts
Supported Work Items
|
Supported Work Item Type |
Applicable Repository Versions |
Unique URL? |
|---|---|---|
|
Task |
Any supported repository version: |
Yes |
Supported Containers
|
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 |
Supported Field Types
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.
|
Field Type |
How is field type referenced in the repository? |
Sample Repository Fields Supported |
Particular Repository Fields NOT Supported |
|---|---|---|---|
|
|
String, ID |
Title, Sprint |
|
|
|
List, Lookup List |
Status, Priority |
|
|
|
Multi-select List |
Strategic Objectives |
|
|
|
Boolean, Checkbox |
Active, Documentation Approved |
|
String