Connects a Change Request to a Change Order associated with implementing the proposed change.
When to use it
The Change Cockpit is the main UI for managing change types and their relationships. Use Change Request – Change Order to connect the proposal with the record coordinating its implementation.
Records and direction
- Relationship type: Non-structure. Associates the records without creating a parent-child hierarchy.
- From: Change Request.
- To: Change Order.
How to use it
- Create the relation with drag and drop in a Structure widget: drag the intended Change Order onto the Change Request it relates to. Select Change Request – Change Order, review the source, target, and any offered values, then confirm.
- Alternatively, use Connect from the source record and choose the target and Change Request – Change Order relationship from the available options.
- Review the resulting connection in the structure or related information. Check the selected records, their versions where applicable, and the relationship filters if the link is not visible.
Example
Improve Seal Design is connected to Implement Seal Redesign. Reviewers can follow the proposed modification into the associated implementation work.
What to check
The proposal and implementation coordination records are associated. Their states and responsibilities remain part of their own managed processes.
Choosing the relationship
This relationship is non-structure. Change Order – Change Task organizes the activities beneath a Change Order. Connecting a proposal to an order is not itself an approval decision.
Related relationship articles
Change Order – Change Task | Affected Item | Change – Impact
