Routes & Tasks

Create Route

Click on the ENOVIA Top Bar.
Select General > Create Route Wizard. . . .

Access the Routes Summary page, Collaboration and Approvals App > Routes > Routes Summary.
Select > Create Route Wizard. . . .

The Step 1 of 4: Specify Details page displays.

Enter the required fields:

Field	Description
Name	AutoName is checked by default. You may name your route, however, to avoid duplicate names, it is recommended that you allow the system to name your route.
Template	Select a route Template for the route (optional)
Description	Enter a meaningful Description for the route
Route Base Purpose	Route Base Purpose determines the types of tasks in the route: Approval -- The route includes only tasks that require the assignee's approval. Review -- The route includes only tasks that require the assignee's comment. Standard -- The route can include tasks that require the assignee's approval or comment or tasks intended only for notification or information.
Scope	The scope for a route determines who can be assigned tasks in the route, who can access the route, and in some cases, what content can be added to the route: All -- any user in the system can be added to the route, including Roles and Groups. Organization -- only members of the selected Organization can be added to the route. Select -- you may select from projects in which you are a project owner or lead and only members and content from that project can be added to the route.
Route Completion Actions	Select the action taken when the route completes: Notify Route Owner Promote Connected Object
Start Route	Select to Start Route Upon Wizard Completion or Manually.
Auto Stop on Rejection	Select the route stop upon an associated task rejection: Immediate -- The route stops immediately. Deferred -- The route stops after other tasks at the current level are completed or rejected.

Click Add Content on the page tool bar to add content, such as a document to review, to the route.
Click Next.

The Step 2 of 4: Select Route Members window displays.

Add all the people to whom you would like to assign tasks.

Click on the page tool bar.
Select Add People.

Other options include Add People by Project, Add Role, Add Group, and Add Member List.

Search for and select a person and click Done in the Select People window.
Repeat to add more people.
Set each person's route access using the Access column pull down list.

This access level is for the route only and not for the content. Groups and roles are added to the route with Read access.

Read -- members can view the Properties page for the route, including all tasks, history, and accesses for the route.
Read Write -- members can also check in files to the route.
Add -- in addition to Read Write permission, members can also add new content to the route.
Remove -- in addition to Read Write permission, members can also remove content from the route.
Add Remove -- in addition to Read Write permission, members can both add and remove content in the route.

Click Next.

The Step 3 of 4: Define Route Tasks window displays.

Enter the Title, Action, Order.

Title - name the task.
Action - set the action required by the assignee.

Route Base Purpose determines the types of tasks in the route

Approve: Assignee may Approve Reject or Abstain Task, while providing a Comment
Comment: Assignee must Complete Task while providing a Comment
Notify: Assignee is not required to take any action.

Order - define the layer of the task in the route.

Enter Assignee & Instructions for a given task.

Be as descriptive as possible to avoid confusion.

Enter the Due Date & Time.

Click the calendar icon to select a date or choose one of the other options

Allow Delegation: the assignee can delegate the task to another person.

Requires Owner Review: When the task is complete, the route owner is notified. The owner must enter a comment and then promote or demote it. The next task in the route is not created until the current task is promoted. Demoting changes the task state back to Assigned and the assignee must complete the task again based on the comment. When a task is demoted, the owner can reassign it to someone else.

Click > Add Task, to repeat steps 12 - 14 for additional tasks.
Click Next.

The Step 4 of 4: Action Required window displays.

Set the Action Required field to determine if All tasks must be finished to complete the route or if Any will complete the route.

NOTE: If an Order of completion was set on the previous screen, this screen shows the task sequence with no selectable options. The default is All.

Click Done.

The Route: Properties page displays.

If the state of the route is Started, then Tasks are sent to the appropriate people.