Skip to main content
Planview Customer Success Center

Planview PPM Pro

101385651.jpg

 


 

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 Hub. Note that additional fields for synchronization or configuration of queries may be required depending on the requirements of your integration.

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.'

Learn how to create a custom user in Planview PPM Pro here. The User Type for Hub integrations should be ‘WS API User.’

Connecting to the Planview PPM Pro Repository

Standard Authentication

Required Fields:

  • URL

  • Username

  • Password

    • Note: To improve performance, we recommend using an authentication token in the password field (though password will still work). Learn how to generate an authentication token here.

Optional Fields:

  • 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.

Screenshot 2023-10-05 at 1.53.27 PM.png

SSO Authentication

Additionally, Planview PPM Pro supports the following SSO implementations:

  • Script (HTTP cookies)
  • X.509 Certificate

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

 


 

Other Configuration Settings

Repository Query

To improve the performance of your integrations, we recommend using a repository query when configuring your Planview PPM Pro collections.

Learn more about creating repository queries here.

Rich Text

Supported rich text elements are: 

  • All standard HTML elements (headings, bold, italics, underline, tables, lists, etc)

Person Reconciliation

For person reconciliation, the following fields are available:

Fields Used for Hub’s Default Person Reconciliation Algorithm

(Standard Field)

Field Names for Person Reconciliation Extensions

Label in Planview PPM Pro

ID

1164

ID

Username

2303

Username

Email

1115

Email

N/A

1103

First Name

N/A

1104

Last Name

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:

  • Comments
  • Associated Tasks
  • Actual Hours

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

 


 

Supported Features

Special Features Supported

You can learn more about special features in Planview Hub here.

Feature

Applicable Hub Version

Applicable Repository Versions

1checkicon.png Time Worked (Worklogs)

1checkicon.png Impersonation

Planview Hub: 20.1 and later

Any supported repository version:

1checkicon.png Comments

1Not_allowed.svg.png Impersonation 

1Not_allowed.svg.png Public/Private 

Planview Hub: 20.1 and later

Any supported repository version:

1Not_allowed.svg.png Attachments

Planview Hub: 20.1 and later

Any supported repository version:

N/A - State Transitions

(PPM Pro does not use state transitions. Status can flow out of or into PPM Pro as a single-select.)

Planview Hub: 20.1 and later

Any supported repository version:

 


 

Supported Artifacts

Supported Work Items

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

Supported Work Item Type

Applicable Hub Versions

Applicable Repository Versions

Unique URL?

Task

Planview Hub: 20.1 and later

Any supported repository version:

Yes

Supported Containers

Learn more about containment in Planview Hub here

Containers that can synchronize between repositories

Applicable Hub Versions

Applicable Repository Versions

Unique URL?

Project

Planview Hub: 20.1 and later

Any supported repository version:

Yes

Containers used to define the boundary of a collection

(when clicking 'Manage Projects' on a collection)

 

 

 

N/A (entire Planview PPM Pro repository is used)

Planview Hub: 20.1 and later

Any supported repository version:

N/A

Containers used for artifact routing

 

 

 

Projects

Planview Hub: 20.1 and later

Any supported repository version:

N/A

 


 

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.

Field Type

Does Hub support custom fields of this type?

How is field type referenced in the repository?

Sample Repository Fields Supported

Particular Repository Fields NOT Supported

1checkicon.png String

1checkicon.png

String, ID

Title, Sprint

 

1checkicon.png Single-select

1checkicon.png

List, Lookup List

Status, Priority

 

1checkicon.png Multi-select

1checkicon.png

Multi-select List

Strategic Objectives

 

1checkicon.png Boolean

1checkicon.png

Boolean, Checkbox

Active, Documentation Approved

 

1checkicon.png Date

1checkicon.png

Date

Date Approved

 

1checkicon.png Date Time

N/A

Date

Last Modified Date

 

1Not_allowed.svg.png Duration

 

 

 

 

1checkicon.png Double

1checkicon.png

Number, Money, Float

Revenue, Estimated Hours

 

1checkicon.png Long

1checkicon.png

Integer

Time Criticality, Number

 

1checkicon.png Person

1checkicon.png

List

Created By, Approved By

 

1checkicon.png Persons

1checkicon.png (as multi-select field)

Multi-select List

Team Members

 

1checkicon.png Relationship(s)

Learn how to configure relationships in Planview Hub here.

N/A

Parent, Associated Tasks

Parent, Associated Tasks

 

1checkicon.png Rich Text

1checkicon.png

Text, Text Box

Description, Objective

 

1checkicon.png Location

N/A

N/A

URL

 

1Not_allowed.svg.png Web Links

 

 

 

 

1Not_allowed.svg.png Time Entries

 

 

 

 

1Not_allowed.svg.png Other

 

 

 

 

 


 

Functional Limitations

Category

Limitation

Applicable Hub Version

Applicable Repository Version

Feature Unsupported

Integer Fields

Integer fields with values that are larger than the largest allowable Java Long value cannot be synchronized.

Planview Hub: 20.1 and later

Any supported repository version:

Feature Unsupported

Duration Fields

The Duration field cannot be updated directly, but can be set by setting Start Date and Target Date.

Planview Hub: 20.1 and later

Any supported repository version:

Feature Unsupported

Read-Only Fields

Sync with LeanKit, Cost Budget and Hours Budget fields are read-only.

Planview Hub: 20.1 and later

Any supported repository version:

Third Party Functional Limitation

Integers

Integers larger than 15 characters may lose precision (ie. with the digits after the first 15).

Planview Hub: 20.1 and later

Any supported repository version:

Third Party API Limitation

Multi-select Fields

Multi-select fields that have options containing commas are unsupported. This is a limitation of the PPM Pro Product.

Planview Hub: 20.1 and later

Any supported repository version:

Third Party API Limitation

Single Selects

List fields that are using “PickList: Resource + Primary Role” are supported as Single Selects rather than Persons.

Planview Hub: 20.1 and later

Any supported repository version:

Third Party API Limitation

Persons

MultiSelect List fields that contain Persons as options are supported as MultiSelects. These Persons cannot contain commas in their names.

Planview Hub: 20.1 and later

Any supported repository version: