Strategy Structure

Last updated
Save as PDF

Overview

The Strategy Structure in Portfolios enables users to centralize and manage enterprise strategies, projects, and products within a unified framework, facilitating comprehensive strategic planning and performance tracking from a top-down perspective.

Creating an integration leveraging the Strategy Structure allows you to synchronize your strategically planned initiatives or capabilities from the Strategy Structure with external tools, such as Planview AgilePlace. This integration facilitates seamless data exchange and collaboration, ensuring that your strategic plans are accurately reflected and executed across multiple platforms.

Setup Details

This section describes the basic settings needed to synchronize the Strategy Structure with supported Planview products. Note that additional fields for synchronization may be required depending on the requirements of your integration.

Global Options

Please ensure that the following global options in Portfolios are enabled:

Enable Entity Last Updated on Auditing (GO 4220)
- When enabled, this global option helps track the last modified date for Strategies. This information is used in the Retrieve Strategy & Collection Search endpoints.
- If this global option is not enabled, please contact customer care for assistance.
Enable Strategic Lifecycles
- When enabled, this global option ensures that LifeCycle attributes for Strategies can be updated.

Feature Flags

Please ensure that the following feature flags in Portfolios are enabled:

EnableFireTriggersAndCheckConstraintsForSqlBulkCopy
- This feature flag should be enabled by default. If not enabled, please contact customer care for assistance.

Supported Features

Special Features Supported

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

Feature	Custom Type Supported?	Applicable Hub Versions	Applicable Repository Versions
Time Worked (Worklogs) Impersonation
Comments Impersonation Public/Private
Attachments Impersonation
State Transitions

Supported Artifacts

Supported Work Items

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

Supported Artifact Type	Applicable Hub Versions	Applicable Repository Versions	Unique URL?
All artifacts under Level 2	Planview Hub: 24.3 and later	Current On Demand (Cloud) 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?
Strategy at Level 2 Note: Beginning in Hub version 22.4, containers can be treated as work items. Learn more here.	Planview Hub: 24.3 and later	Current On Demand (Cloud) Version	Yes
Containers used to define the boundary of a collection (When clicking 'Manage Projects' on a Collection)
N/A
Containers used for artifact routing
Strategy at Level 2	Planview Hub: 24.3 and later	Current On Demand (Cloud) 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.

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

Functional Limitations

Category	Limitation	Applicable Hub Versions	Applicable Repository Versions
Third Party Functional Limitation	Multi Person Field Types Multi Person field types are not supported.	Planview Hub: 24.3 and later	Current On Demand (Cloud) Verison
Third Party Functional Limitation	Investment Approval Field The Investment Approval (ProductInvestmentApproval) field is supported as read-only.	Planview Hub: 24.3 and later	Current On Demand (Cloud) Verison
Third Party Functional Limitation	Financial Allocation Field The Financial Allocation field is not supported. For any work allocated to Strategy, the financial allocation will always be 100% by default.	Planview Hub: 24.3 and later	Current On Demand (Cloud) Verison
Third Party API Limitation	Epic Card Field The Epic Card (WebLinks) field is supported as read-only.	Planview Hub: 24.3 and later	Current On Demand (Cloud) Verison
Good to Know	Work Deleting work from the Strategy screen deletes the work artifact, not just the association.	Planview Hub: 24.3 and later	Current On Demand (Cloud) Verison
Good to Know	PPL Work PPL work can only be assigned to Strategy.	Planview Hub: 24.3 and later	Current On Demand (Cloud) Verison