Routes & Tasks Overview
Routes & Tasks OverviewA Route is a formally documented review process for tracking object information, communication, and approvals, among other things.
Use a Route when you need to record the review/approval of an object such as ECs, parts, or documents.
Tasks are individual work assignments within a Route.
Reviewers must perform an action (Approve, Reject, Complete (with Comments)) on assigned Tasks to satisfy its conditions.
When initiated, Routes generate Tasks.
When creating a Route, assign Tasks to as many recipients as necessary and provide clear instructions for each assignee.
The system manages Task notifications and emails the assignees.
Tasks can be staggered in a multiple-tier Route, so assignees receive Tasks after other Tasks are completed.
ECs and Info Trackers utilize Routes and Tasks to automate information gathering, reviews, and approvals.
Tasks can be assigned in ENOVIA without going through the steps of creating a Route.
Individually assigned Tasks are still part of an ENOVIA Route, which is displayed on your My Routes page.
See View Routes.
Part, EC, Info Tracker, and Project Routes and associated Tasks are displayed on the object Approvals/Tasks and Routes tabs of the Lifecycle page, accessed on the category tree.
Tasks maybe added directly on the object Approvals/Tasks tab.
See Add Tasks and Routes.
Pages with lists of objects, such as Parts, ECs, or Documents, include
a tool bar command 
to launch Collaborator.
In Collaborator, you may add objects from the current screen, select ENOVIA users, and create Tasks.
Automatic Routes are set up by the Project Owner for a specific object (i.e., EC or part) in the project. When the object reaches specific conditions, such as a certain lifecycle state, the Route is engaged and Route Tasks are automatically generated.
Ad hoc Routes are manually created by users and attached to objects.
When a Route is completed, one of two actions is initiated:
Promote Connected Object (Default ) - When all Route conditions are met, the system automatically moves the associated object to the next lifecycle state. This completion action is useful when an object should be reviewed prior to promotion.
Notify Route Owner - The system sends an email notification to the Route Owner informing that all Route conditions have been met. This action is most useful on documents, which have only one lifecycle state.