Review and Approve the Package and Summary Reports
Participants identified in the Define Distribution List receive review and approval tasks, which appear in their My Tasks table. Depending on the selected routing process, participants can do the following actions:
• Content routing: Contributors add the necessary content and complete their assigned tasks. Once completed, the package transitions from the In Work state to the Completed state.
• Approval routing: Reviewers examine the package contents. If the content is accurate, approvers can approve it, advancing the package to the Approved state even if reviewer tasks are still pending.
◦ Rework: If any approver requests rework, the package enters the Rework state. After all approvers finish their reviews, a rework task is assigned to the package creator. Once rework is completed, the package can be routed again for approval. Review and tracking tasks are removed from task lists after final approval.
• Dependency review routing: Approvers must approve both the dependent objects and the summary reports to apply the replication lock to the package contents.
◦ Approve: If all approvers approve, the package moves from Evaluation state to Locked state, regardless of reviewer’s task completion. The objects are marked with the Locked for Replication status, making them eligible for replication. Upon import, source objects overwrite the target objects.
◦ Rework: If an approver requests rework, the package enters the Rework state, and the in-transit locks are removed. 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 tracking tasks are removed from the task lists after the approval tasks are complete.
◦ Reject: If an approver rejects the package, all pending review tasks are promptly canceled. After every approver has completed their action, whether approving or rejecting, the package is marked as Rejected, and any in-transit locks on its objects are removed, making them available for modification.
 |
• If an error occurs during approval, rejection of summary reports, or while moving the package to the rework state, the routing process fails. However, the in-transit lock remains active on the affected objects.
• If the replication lock fails to apply, review the Summary_Open_Workflows.csv report for any active workflows associated with the objects in the Context Collector or Object Collector package. If workflows are found, terminate them gracefully and restart the routing process. For more information, see Replication Summary Reports.
• If the package contains only managed baselines, electrical parts, or objects that are not supported for replication, a task is still generated. However, when the package is approved, the replication lock is not applied to the package contents.
|