Review and Approve the Package and Summary Reports
Once the distribution list is defined, designated participants receive review and approval tasks, which appear in their My Tasks table. Based on the routing type, participants can perform the following actions:
• Content routing: Contributors can add the necessary content and complete their tasks. Upon task completion, 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, 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 assigned to the package creator after all approvers have completed their reviews. Once the rework is completed, the package can be rerouted for approval. Review and tracking tasks are removed from task lists once approval is finalized.
• Dependency review routing for Disowning by Replication: Approvers must validate dependent objects and summary reports to convert replicated data into local data within the package.
◦ Approve: When all approvers give their consent, the package transitions from the Evaluation state to the Succeeded state, even if reviewers haven’t completed their tasks. Eligible contents are then converted from replicated data to local data.
◦ Rework: If any approver requests rework, the package moves to the Rework state. All selected replicated objects remain unchanged. After all approvers complete their tasks, a rework task is assigned to the package creator. Once rework is completed, the package can be resubmitted for approval. Review and tracking tasks are removed once approval is finalized.
◦ Reject: If an approver selects Reject, all pending review tasks are marked as rejected. After all approvers complete their tasks, the package transitions to the Rejected state. The selected replicated objects remain unchanged.
 |
• If an exception occurs during the dependency review routing process such as while approving/rejecting summary reports or transitioning to the Rework state the routing process fails. In such cases, all selected replicated objects remain unchanged.
• If the package contains only managed baselines, electrical parts, or objects not supported for replication, a task is still generated. However, upon approval, the Locked by Product Design Package status remains unchanged for the replicated objects.
|