Planview Portfolios

Key Features and Benefits

• Synchronizes artifacts across the lifecycle, allowing information to flow freely between Planview Portfolios and other tools
• Improves collaboration between the PMO, development, test, the service desk and more
• Provides visibility to PMO office of the status of ongoing projects
• Supports cross-tool traceability and reporting, removing the need for manual processes and spreadsheets

Common Integration Patterns

• Associating Planning Items to Implementation Artifacts 
• Associating Planning Items to Requirements
• Aligning Testing Teams across Testing Tools
• Populating Requirements into PLM Tools

Demo Videos

Minimal User Permissions & Hub User

We recommend that you create a new user within your external tool, to be used only for your Hub integration. This is the user information you will enter when setting up your repository connection within Planview Hub. By creating a new user, you will ensure that the correct permissions are granted, and allow for traceability of the modifications that are made by the synchronization. 

In general, your user account should have sufficient permissions to create, read, and update artifacts in your repository. However, depending on the use case, your user may need different permissions. For example, if you are only interested in flowing data out of your repository, your user may not need to have full CRUD access, as the 'create' and 'update' permissions may not be needed.

Your user should have a secure password or token. Please be aware that Hub will not allow you to save a repository 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'

  

• Check 'Use Query Service'

  

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:

• Location/Connection 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
• 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 Portfolios (see screenshot below).
  • Note: This field is case sensitive.

Optional Fields:

• Worklog Submission Status: This field is only applicable for Planview OEM customers. Other customers can leave this field blank.
• Allow Update of Protected Timesheets: This field is only applicable for Planview OEM customers. Other customers can leave this field blank.
• Throttling Settings: This field indicates the number of API calls that can be made per minute. See details here.
  • Note: This field should only be set under the guidance of customer care as the ideal value is highly dependent on each customer's unique environment. 
• Connection Security: If checked, insecure connections to this repository will be allowed. See details here.

SSO Authentication

Additionally, Planview Portfolios supports the following SSO implementations:

• Script (HTTP cookies)
• X.509 Certificate

Learn more about how to set up your repository in Planview Hub here. 

Primary Structures 

Navigate to Primary Structures to see your instance's planning levels:

Navigate to Global Options to see which artifact is defined as the Primary Planning Level:

Note: Hub does not support configurations where the Primary Planning Level (PPL) is set to level 1 or 2.

In Planview Hub 18.3.2 and later:

All primary structures defined below the Primary Planning Level (PPL) will be treated as work items in Planview Hub. The primary structure defined as the Primary Planning Level (PPL) will be treated as a container in Planview Hub. Both work items and containers can be synchronized between Planview Portfolios and other tools.

Note: Hub does not support configurations where the Primary Planning Level (PPL) is set to level 1 or 2.

Learn about the difference between containers and work items in Planview Hub here. 

In Planview Hub 17.1 - 18.3.0.20180620-b378:

All primary structures defined below the primary planning level will be treated as artifacts for synchronization. The Primary Planning Level cannot be synchronized to other tools.

Note: Hub does not support configurations where the Primary Planning Level (PPL) is set to level 1 or 2.

Strategy Structures

Person Reconciliation

For person reconciliation, the following fields are available:

For field based (advanced) person mapping scenarios, you can choose to use any of the following person object fields. 

• Available fields: person-email, person-id, person-resource-code, person-display-name
• Default: person-id
• Person-resource-code can be found in the URL, as shown in the screenshot below

Learn more about how to configure person reconciliation in Planview Hub here.

Full Scan

Due to third party API limitations, updates to the following fields may not trigger change detection or cause a synchronization immediately. To ensure these updates synchronize, a high fidelity full scan must occur or another qualifying change must be made to the artifact:

• Custom Fields
  • Note: custom single-select fields do not require a full scan
• Persons (Multi-Person) fields (i.e. Assignees, Reversed)
• Duration fields

Learn more about how to configure change detection and full scan intervals in Planview Hub here. 

Special Features Supported

Supported Work Items

Learn about the difference between containers and work items in Planview Hub here. 

Supported Containers

Learn more about containment in Planview Hub here. 

---

 

Supported Field Types

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 synchronize properly.

Standard field type	Is this field supported for the Strategy artifact?	Does Hub support custom fields of this type?	How is field type referenced in the repository?	Sample repository fields supported
String			Text   Strategy artifacts: Text Long Text	Revision Key Seq-ID Description Work ID   Strategy artifacts: Strategy Seq. ID Description Benefits Anticipated Key Objective
Single Select			Strategy artifacts: Alternate Structure	Work Status   Strategy artifacts: Status Strategy Type
Multi Select Supported in Planview Hub 19.1 and later, Tasktop Sync 4.17 and later			Strategy artifacts: Alternate Structure	Strategy artifacts: Releases Outcome Breakdown
Boolean Only supported for Strategy artifacts			Boolean	Has Children Enable Lifecycle
Date
Date Time			Date/Time	Scheduled Start Scheduled Finish   Strategy artifacts: Target Finish Target Start
Duration			Strategy artifacts: Duration	Spent Duration Effort Fields   Strategy artifacts: Target Duration Work Actual/Schedule Duration Total Effort (FP|FV) Effort: Current Year (FP|FV)
Double			Strategy artifacts: Numeric with non-zero decimal places Currency	Strategy artifacts: Investment Priority Score WSJF (Epic) Actual Costs to Date (FP|FV) Total Baseline Costs (FP|BV)
Long			Numeric   Strategy artifacts: Numeric with zero decimal places	Strategy artifacts: Place Access Level
Person Only supported for Strategy artifacts				Lifecycle Administrator
Persons				Reserved Assignees Allocated Assignees
Relationship(s)		N/A		Parent
Rich Text
Web Links Only supported for Strategy artifacts			URL	Value Stream URL Enterprise Architecture URL
Location Only supported for Strategy artifacts		N/A		Location
Other