Route an Object
You can use several methods to initiate the routing process for an object:
• From the Folder Contents table, select an object and then select > . Or select Route from the right-click actions menu of an object.
• Navigate to the information page of an object and select > .
• Click the route icon 
on the Packages table toolbar.
on the Packages table toolbar. | You must have access to modify an object to route it. |
1. Under the Select Routing Process step, select one of the following routing process options (these options vary based on the type of object you are routing):
Approval Routing | Assign team members to review and approve the routed object. Once all approvers have indicated their approval, the object is set to the Approved state. |
Notify Routing | Send an email notification to a group of team members letting them know that the routed object exists in the project or program. Once the notification is sent, the object is set to the Completed state. |
Release Routing | Assign team members to approve the routed object so that it can be released. Once all approvers have indicated their approval, Windchill sets the object state to Released. |
Review Routing | Assign tasks to team members to review the routed object so that you can gather their input to complete your work. Once all required reviewers have completed their review tasks, the object is set to the Completed state. |
Two Level Approval Routing | Assign two sets of team members to approve the routed object in sequential approval routings. Once all first-level approvers have indicated their approval, the object moves to the Under Review state and the second approval routing begins. Once all second-level approvers have indicated their approval, the object is set to the Approved state. |
Package Approval Routing | Assign package team members a task to review and approve a routed package. Once all approvers have indicated their approval, the object is set to the Approved state. |
Package Content Routing | Assign contributors a task to add content to the routed package. When all contributors have added their content and completed the task, the package moves to the Completed state. |
Package Delivery Routing | Assign package managers a task to deliver the routed package. When one of the managers completes the task, the delivery is marked as Accepted or Rejected accordingly. |
2. Under the Define Distribution List step, the roles that appear are based on the routing process option you selected in the previous step. You can select one of the following role options for each of the listed members or groups. Or you can use the Check All checkbox to select all participants for a role.
Author | Responsible for editing and maintaining the routed object. This role is optional. |
Assignee | Receives an email notification for the routed object. |
Approver | Must approve, reject, or request additional work on the object for the routing process to continue. |
Reviewer | If the Review Routing option is selected, then the Reviewer must complete a review task for the routing process to continue. This role is optional for other types of routings. On routes that include an Approver role, once the routed object is approved, all uncompleted review tasks become obsolete. When using the Review Routing process, only one reviewer must complete the task for all reviews to be considered complete. |
Observer | Views the object and can optionally submit comments; however, the routing process can continue regardless of whether they complete their routing task. This role is optional. |
Package Approver | Must approve or request additional work on the package for the routing process to continue. |
Package Contributor | Adds applicable content to the package and completes the task. |
Package Reviewer | Can review the package and submit comments; however, completion of this review task is not required for the routing process to continue. This role is optional. |
Package Manager | Delivers the package and completes the task. |
3. Under the Specify Instructions step, provide any notes or special instructions in the fields provided.
4. Under the Specify Due Date step, click the calendar to select a due date 
.
.Alternatively, you can enter a duration for each applicable routing activity. (Not all routing activities include a due date or duration).
◦ Select Notify assignee to have an email reminder sent to the routing process participants who must complete tasks.
◦ Select Notify routing initiator to have an email sent to yourself if the routing process tasks have not been completed.
Notifications are sent based on the specified number of days before the due date.
5. Under the External Participants step, you can choose to notify additional participants that were not included under the Define Distribution List step.
a. Enter an email address in the table row.
▪ Click the add row icon 
or the add five rows icon 
to include additional participants.
or the add five rows icon to include additional participants.▪ Select a row and click the remove row icon 
to remove participants.
to remove participants.b. Select the Include Document checkbox to include a link to the information page in Windchill.
6. Click Finish.
| | Depending on the workflow process rules set at your site, you might see an additional step requiring an electronic signature. |
The routing process begins and email notifications are sent to participants. Any tasks appear in the Tasks table, and (if applicable) notifications and tasks are created as the object progresses through the routing process.
Once this routing process has completed, the object can be routed again.
| | If your site has defined its own routing processes, it is possible that email notifications might not be sent, depending on the definition of the process. |