Workflows in PM Compass are capable of having parent/child relationships.
An example of where this applies is for a potential risk to a project. You can create a Project Risk that contains information about the project’s risk. This needs mitigation steps or actions that are taken to prevent or reduce the impact of the risk to the project. You can assign the actions associated to a specific Project Risk to different people who are responsible for ensuring that the action is completed. A high-level person such as a CAM (Control Account Manager) manages Project Risks. They ensure that assignees perform all of the actions for the risk. A mitigation step action can also have workflow steps associated to it.
In this scenario, the Project Risk is considered the parent and the mitigation steps or actions are the child workflows that are linked subordinately to the parent Risk. You can configure a workflow type to have a relationship with other workflows, that is, a parent/child relationship. You can configure it to be a parent, a child, or have no relationship with other workflows. You can set this in Workflow Type Configuration.
These are workflows that can have relationships with child workflows.
These are workflows that can have relationships with parent workflows.
When you start a workflow, the child workflows are updated with the status date and the planned effective date of the parent workflow.
During the Apply Cost Changes process when the calendar is advanced on the sandbox (because the live project had its calendar advanced since the workflow was created), PM Compass updates both the parent workflow and the child workflows with the status date of the live project.
You can set the Relationship with Other Workflows field on the General tab of Workflow Type Configuration to:
None if a workflow type does not have to be a parent or a child. This means that the workflow will not have a relationship with any other workflow. It can be neither a parent nor a child.
Workflow Can Be a Parent which means that you can link child workflows. A parent workflow can have one or more linked children or can have no children.
Workflow Can Be a Child which means that it can either be a child of a parent or not be linked to another workflow. It cannot have a child workflow linked to it. Only parent workflows can have children.
See the General tab of Workflow Type Configuration for more information
Learn about the parent/child workflow steps