Route the Package
Routing Overview
Routing assigns tasks to team members for adding, reviewing, and approving package contents.
Email notifications are sent to:
• Assignees for task action.
• Package creator for tracking progress.
The package creator can also force-approve a task if needed. This removes the task from the assignee’s list and completes the routing. Notifications are also sent when a task is completed or fails.
Steps to Route a Package
To route a package, do the following:
1. In the Route window, under Select Routing Process, select Dependency Evaluation and Disowning the Replication for Object Collector Package or Dependency Evaluation and Disowning the Replication for Context Collector Package to initiate the conversion of replicated data to local. If required, you may also select other routing process options before proceeding with disowning by replication.
Available routing process options include:
◦ Content Routing for Object Collector Package or Content Routing for Context Collector Package: Assigns contributors the task of adding content to the routed package.
◦ Approval Routing for Object Collector Package or Approval Routing for Context Collector Package: Assigns reviewers and approvers a task to review and approve the contents of the routed package, respectively. The review task is optional in the routing process. When routed for approval, the package moves to the Under Review state.
◦ Dependency Evaluation and Disowning the Replication for Object Collector Package or Dependency Evaluation and Disowning the Replication for Context Collector Package: Collect the dependent objects associated with the selected replicated items in the package, and assign tasks to reviewers and approvers to evaluate and approve the summary reports generated during the routing process. The review task is optional. To initiate this dependency review, you must be a member of the Replication Authority group. The package transitions to the Evaluation state during dependency collection, and then to the Summary and Review state.
 |
In this document, both the routing options Dependency Evaluation and Disowning the Replication for Object Collector Package and Dependency Evaluation and Disowning the Replication for Context Collector Package are collectively referred to as dependency review routing disowning by replication.
|
2. In Define Distribution List, select the participants who will be assigned tasks for adding content, reviewing, or approving the package or its summary reports. To perform these actions on a Context Collector Package, participants must be members of the Replication Package Administrators group. Additionally, reviewers and approvers involved in the dependency review routing for disowning by replication must belong to the Replication Authority group.
3. (Optional) Perform the following steps:
◦ Specify Instructions: You can provide notes or special instructions.
◦ Specify Due Date: You can enter a duration for the routing activity or click the calendar to select a due date.
◦ External Participants: Yo can choose to notify additional participants who were not included in the Define Distribution List.
4. Click Finish to initiate the routing process.
Routing Outcomes
If the dependency review routing for disowning by replication completes successfully, the selected replicated objects and their dependent objects within the package are converted to local. Once converted, these objects can be freely modified on the target system.
The image below shows the state before the disowning by replication process.
The image below shows the state after the disowning by replication process.
If the dependency review routing action fails, the Locked by Product Design Package status remains unchanged for the replicated objects in the package, and the package transitions to the Failed state.
This failure can occur under the following conditions:
• None of the objects in the package is eligible for disowning by replication. For example, electrical parts, managed baseline, or objects not supported for replication.
• All the objects in the package are already local.
• The package does not contain any object.
• An error or exception occurred when collecting the dependent objects.
If at least one object in the package is eligible for disowning by replication, the process proceeds successfully, and summary reports are generated for the routed package. These reports indicate which objects can be converted from replicated to local data
For more information, see Replication Disowning Summary Reports.