This article covers how Linked Entities work on View pages in PPO.
- Introduction
- What is automated linked entities?
- How does it work?
- Why would I see a blank linked entity list on a view page?
Introduction
PPO supports linking of entity items in various ways.
- You can manually add a document against a Project to plug a governance requirement or to add any other document artifacts to a project. This will show as a table under your Project View page.
- If a document is added, you can edit an entity item like a Risk, Issue or Scope Change, and link a document to the specific entity record.
- Automated linking is also supported by means of Programme List, Project List and Entity List Type fields.
Below we will focus on how PPO automates linking of entities on View pages.
What is automated linked entities?
Automated linked entities functionality allows you to view items that are related to the current entity item from its view page using Programme List, Project List and Entity List type fields.
How does it work?
On a View page, it will display related records in a table whenever another record references the current entity records via a List type field (mentioned above). See below examples:
Example 1: Project Entity
PPO supports Parent Project functionality. A Project List type field exists on the Project entity to support this. In the below example, Northern Frontier Marketing is a Parent Project.
Due to the Parent Project field being a Project List type field, you will see a table for Projects above the History section.
If you go to the View page of the Parent project, there will be a table showing all the projects linked to it using the Parent Project field.
Example 2: Sprints & Work Items:
In PPO, you have the ability to link a Work Item to a Sprint. This means, that on a Work Item record itself, there is a Sprint Entity List Type field:
Due to the Work Item having the Sprint Entity List type field, it creates a relationship with the Sprint entity. In linking a work item to a sprint, when viewing a Sprint View page, you will see a table reflecting all the work items related to that Sprint. Screenshot example below.
Why would I see an empty linked entity list on a view page?
In the Sprint and work item example, if no work items have been allocated to a Sprint, you will still see an empty table for Work Items due to the fact that on the Work Item entity, a Sprint Entity List type field exists.
The below example is a Sprint View page, that shows an empty work item list because no work items have been linked to it.
To learn more about Entity List Type fields, click here.