Planview ProjectAdvantage

Key Features and Benefits

• Real-Time Portfolio Visibility: Pulling live data from ProjectAdvantage means your teams always have an up-to-date picture of project status, resource availability, and budget health, no manual exports or stale spreadsheets.

• Eliminate Duplicate Data Entry: By connecting ProjectAdvantage to your existing tools, updates made in one place are reflected across all your tools, reducing errors and saving time across your organization.

• Stronger Strategic Alignment: ProjectAdvantage is built to connect day-to-day execution to organizational strategy. Integrating it into your ecosystem means that strategic priorities flow directly into the work your teams plan and execute.

Common Integration Patterns

• Associating Planning Items to Implementation Artifacts 

• Associating Planning Items to Requirements

• Populating Requirements into PLM Tools

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

See here for instructions on creating a custom user and external application in ProjectAdvantage.

List of minimal user permissions:

The token generated from the Designer application already includes the required permissions by default. In most cases, no additional permissions need to be assigned.

However, the required permission scopes may vary depending on the artifact type and the operations being performed. For the artifacts currently supported, the following permission scopes are required:

• project:read

• projects:write

• user-defined-categories:read

• user-defined-categories:write

Ensure that these permission scopes are available to allow the connector to function properly.

Connecting to the ProjectAdvantage Repository

OAuth 2.0 Client Credentials Authentication (Recommended)

The repository can be configured with OAuth 2.0 standard parameters using Client ID, Client Secret and Permissions. These parameters can be generated by creating an external application on the ProjectAdvantage UI. To create an application, please see the details here.

Required Fields:  

• Location/Connection URL  

• Example Format: https://sagrawal003.white-sciforma.net/sciforma/rest/  

• Client ID (Get it from the external application window on ProjectAdvantage) 

• Client Secrets (Get if from the external application window on ProjectAdvantage) 

• Permission/Scope (mentioned above) 

Optional Fields:  

•  Throttling Settings: This field indicates the number of API calls that can be made per minute.  

• By default, ProjectAdvantage has a limit of 150 API calls (all the APIs) per Second for each user account. When setting up your ProjectAdvantage repository, a recommended setting for this field is 5000 API calls per minute. If you experience performance delays, this limit can be raised with assistance from customer care. If your user account rate limit is raised or lowered, you will need to change the setting in the Hub configuration to always be slightly lower than the limit defined by ProjectAdvantage. 

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

API Token Authenticator

Required Fields: 

• Location/Connection URL 

  • Example Format: https://sagrawal003.white-sciforma.net/sciforma/rest/

• API Token

  • Users can generate the token in the ProjectAdvantage designer

Optional Fields: 

• Throttling Settings: This field indicates the number of API calls that can be made per minute.

  • By default, ProjectAdvantage has a limit of 150 API calls (all the APIs) per second for each user account. When setting up your ProjectAdvantage repository, a recommended setting for this field is 5000 API calls per minute. If you experience performance delays, this limit can be raised with assistance from customer care. If your user account rate limit is raised or lowered, you will need to change the setting in the Hub configuration to always be slightly lower than the limit defined by ProjectAdvantage. 

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

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

Rich Text

All rich text elements are supported.

State Transitions

State transition is supported using the Single Select data type. Any field configured as a Single Select type can be mapped to the target repository’s states. 

For example, the following fields in ProjectAdvantage represent the state of a Project or Task artifact: 

• Workflow 

• Workflow State 

Learn more about how to configure state transitions in Planview Hub here.

API Rate Limiting:

In Planview Hub 21.4, a new Throttling Settings field was added to limit the number of API calls per minute to a repository. By default, the ProjectAdvantage repository implements an API rate limit of 150 API calls per second per user account. This limit can be raised or lowered upon request to ProjectAdvantage. 

When setting a value in the Throttling Settings field, you should set it to a value lower than the ProjectAdvantage repository API limit (i.e., 150). The suggested value is 140. 

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

Person Reconciliation

For person reconciliation, the following fields are available:

Learn more about how to configure person reconciliation 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. 

Learn more about containment in Planview Hub here.