Planview Portfolios
Overview
Organizations can improve their ability to manage their application portfolios by ensuring that work performed by the PMO (Project Management Office) is available to other members of the extended development team, and that the PMO has visibility to progress being made on its initiatives and projects.
Connector Setup Details
This section describes the basic steps needed to prepare your Portfolios 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.'
Before connecting to the repository, you must enable query service for the connector to be able to use the web services.
-
Navigate to Global options:
-
Enable Query Services
List of minimal user permissions:
-
The connector needs to comment to the server using an admin user
-
The connector does not support SSO users
-
Role of the user must be PV admin
To create a new user/resource, navigate to Administration settings:
Connecting to the Planview Portfolios Repository
Standard Authentication
Required Fields:
- URL
- Required Format:
- If using an SSO-enabled datasource: https://server.pvcloud.com/planview
- If not using an SSO-enabled datasource: https://server.pvcloud.com/testing
- Required Format:
- Username
- Password
- Data Source Name:
- This is the name of the database you are connecting to, and can be found while logging in to Planview (see screenshot below).
- Note: This field is case sensitive.
Supported Artifacts
Supported Work Items
|
Supported Artifact Type |
Applicable Repository Versions |
Unique URL? |
|---|---|---|
|
All artifacts under the Primary Planning Level |
Any supported repository version: |
Yes |
Supported Containers
|
Containers that can be modeled as Flow Items |
Applicable Repository Versions |
Unique URL? |
|---|---|---|
|
Primary Planning Levels |
Any supported repository version: |
Yes |
|
Containers used to define which artifacts are included in an Artifact Set |
||
|
N/A (entire tool selected as container) |
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.
|
Standard Field Type |
How is field type referenced in the repository? |
Sample Repository Fields Supported |
Particular Repository Fields NOT Supported |
|---|---|---|---|
|
|
Text |
Revision Key Seq-ID Description Work ID |
|
|
|
|
Work Status |
|
|
|
|
|
|
|
|
|
|
|
Boolean
Functional Limitations
|
Category |
Limitation |
Applicable Repository Versions |
|---|---|---|
|
Configuration Requirement |
Multi Select Fields Multi Select fields must be set to have a value. |
Any supported repository version: |
|
Third Party Functional Limitation |
Projects Because Planview Portfolios does not support the notion of ‘projects,' the following behaviors may be observed when using Viz:
|
Any supported repository version: |