1. Get started | 2. Design and set up | 3. Capability usage | 4. Reports and outputs |
Audience |
Planview administrator |
Objective |
Successfully install, configure, and test the Portfolios-ProjectPlace connector. |
Note: for the steps to activate Planview Admin to support the implementation of connected Planview products, see Overview of Planview Admin.
Step | Role | Description | Resources |
Planview administrator Portfolio manager Project manager Team member |
Understand the Portfolios-ProjectPlace connector workflow | ||
Overview of the Portfolios-ProjectPlace connector | Planview administrator | Understand the benefits of connecting governed work in Portfolios to a collaborative workspace in ProjectPlace, and how the connector syncs cards and activities in ProjectPlace to work in Portfolios | |
Request and install the connector | Planview administrator | Request installation of the connector and review the attributes the Portfolios-ProjectPlace connector creates | |
Planview administrator | Validate and test the connector using one of two methods |
Configuring connected templates for hybrid delivery using connected Portfolios-ProjectPlace streamlines the creation of connected projects, standardizes information shared across products, and drives better reporting at the portfolio level.
Step | Role | Description |
Planview administrator |
Create a project in Portfolios under the Parent of WBS templates. Fill out the work breakdown structure (WBS).
Assign a user to the ProjectPlace head workspace administrator.
Sync the project with ProjectPlace (creates a connected ProjectPlace workspace template).
|
Step | Role | Description | Resources |
Configure the connected ProjectPlace workspace template |
Planview administrator |
Fill out all of the desired information and details in the ProjectPlace workspace template. Add boards, create cards, create a document structure, create groups such as external members with group permissions, and associate project activities to the boards and cards. |
Creating a scripted dialog lifecycle step is a best practice to automate the creation of connected projects. As part of this step, you will choose whether to manage the plan (WBS) in Portfolios or ProjectPlace. This table provides a comparison of plan functionality in ProjectPlace vs. Portfolios when you choose to manage the plan in ProjectPlace.
ProjectPlace | Portfolios | |
Plan is read-only |
No |
Yes |
Start/finish dates are editable |
Yes |
Only if there are no activities |
Capture baseline |
Yes, as a snapshot |
Yes |
Revert baseline |
No |
No |
Run the critical path |
No |
No |
Assign and edit resources |
Yes – card assignee |
Yes – reserve, allocation, authorization |
Create milestones |
Yes |
No |
Create or update action items (cards/tasks) |
Yes |
No |
Create, update, and delete activities |
Yes |
No |
Report time |
Yes |
Yes |
Change ownership of the plan |
Yes, if no dependencies |
Yes, if no dependencies |
Set an activity to Done |
Yes |
No |
View card details |
Yes |
Yes |
View activity status and progress |
Yes |
Yes |
Plan supports dependencies |
Yes, Finish-Start |
No |
Add cards (tasks) directly in the plan |
Yes |
No |
Edit the schedule and backlog |
Yes |
No |
Partial plan sync from Portfolios |
No |
No |
Run progression |
Yes |
Yes |
Step | Role | Description |
Create a scripted dialog lifecycle step to automate the creation of connected projects |
Planview administrator |
Configure a new scripted dialog lifecycle step that automatically applies the connected template to a project and syncs the project with ProjectPlace. |
Choose to manage the plan in Portfolios or ProjectPlace | Planview administrator |
Select the option to manage the plan in Portfolios or manage the plan in ProjectPlace. When the plan is managed in Portfolios, there are no changes to plan functionality in Portfolios. When the plan is managed in ProjectPlace, the plan becomes read-only in Portfolios. This comparison table details which plan functionality is disabled in Portfolios when ProjectPlace manages the plan. |
Apply the connected template to a project | Planview administrator |
Create a new project to test and run the script. The script should apply the connected template to the Portfolios project, create a connected ProjectPlace workspace with all the template elements, and ProjectPlace cards create corresponding action items that are added to the plan in Portfolios. |
Monitor project status and progress | Planview administrator |
Monitor and update the project schedule; look for indicators of issues. |
Before users can access the Power BI tiles for the Project Collaboration Dashboard in Portfolios, an administrator must configure the proper tabular model and job streams. After the initial configuration, administrators can modify the out-of-the-box Power BI report to customize the dashboard's report for their users.
Note: if you need additional customization to align the tabular model to your specific needs, such as new alternate structures or custom fields, contact your Planview Managing Consultant or Customer Success Manager to work with Planview Global Reporting Services (GRS).