Review and Approve the Package and Summary Reports
Once the distribution list is defined, the designated participants are assigned review and approval tasks, which appear in their My Tasks table. Depending on the routing type, they can perform the following actions:
• Content routing: Contributors can add the required content and complete the task. Upon completion, the package transitions from In Work to the Completed state.
• Approval routing: Reviewers can review the contents of the package. If the content is accurate, approvers can approve it, moving the package to the Approved state even if reviewers haven’t completed their tasks.
◦ Rework: If any approver requests rework, the package enters the Rework state. A rework task is then assigned to the package creator after all approvers have completed their reviews. Once the rework is done, the package can be rerouted for approval. Review and tracking tasks are removed from task lists once approval is finalized.
• Dependency review routing: An approver must approve both the dependent objects and the summary reports to apply the replication lock on the objects in the package.
◦ Approve: If all approvers approve, the package moves from Evaluation to Locked, regardless of reviewer task completion. The contents of the package are marked with the replication lock, named Locked for Replication, making them eligible for replication. Upon import, target objects are overwritten by source objects.
◦ Rework: If an approver requests rework, the package enters Rework, and in-transit locks are removed from the objects. A rework task is assigned to the package creator after all approvers complete their tasks. Once the rework task is complete, the package creator can reroute the package for approval. The review and track package tasks are removed from the task lists after the approval tasks are complete.
◦ Reject: If an approver selects Reject, all pending review tasks are canceled. The package is marked Rejected after all approvers complete their tasks, and in-transit locks are removed from the objects.
 |
• During the dependency review routing process, if an error occurs while approving or rejecting the summary reports, or when moving the package to the rework state, the routing process fails; however, the in-transit lock on the objects remains in place.
• If you encounter an issue where the replication lock fails to apply, check the Summary_Open_Workflows.csv report for any active workflows related to the objects in the Context Collector or Object Collector package. If found, terminate them gracefully and restart the routing process. For more information, see the section Summary_Open_Workflows.csv in the topic How to View Summary Reports.
• If the package contains only managed baselines, electrical parts, or objects that are not eligible for replication, a task will be generated. However, when the package is approved, the replication lock will not be applied to the package contents.
|