Starting or Resuming a Route

When using the Route wizard to create a route, you have the option of starting it immediately or waiting to start it later. If you created a route but did not start it, you can edit it as required and start it when ready. Routes that you create but do not start have a state of Not Started. Once started, the route state is Started. Only the route owner can start the route.

If there are members in the route who are not assigned a task, the app removes them from the route when you start it.

When you start a subroute, the system makes sure none of the task due dates are later than the parent task's due date. If they are, you must make the due dates earlier.

Required access roles: You must be the route owner to start or resume the route.

Before you begin: Open the required route. See Opening a Route.
Select Start Route or Resume Route from the page Actions menu or toolbar.

If any of the future tasks in the route are assigned to an inactive user, you cannot start or resume the route. You must first reassign those tasks to an active user.

The system changes the route to the Started state and creates each task that has an order number of 1. The task recipients will see the task listed in their tasks list and they will receive notification that the task is pending.

Notifications are managed by 3DNotification. You can view notifications in the Notification Center, and you can select to receive email notifications. Notifications include links to the route or task. Links for routes open the properties for the route in Route Management and links for tasks open in Collaborative Tasks. For more information, see Social and Collaborative: Enterprise Modeling and Execution: Route Management: 3DNotifications for Routes and Tasks.

If the task is assigned to a user group, all people assigned to the user group receive the notification and can access the task. If you receive a message that says no persons were notified, there were no people assigned to the user group who have Read access to the route content. You need to assign the task to someone else. See Route Task Properties.

If you are resuming or restarting a route that has user groups as task assignees, the app checks the value of the Revert User Group(s) Assignment field and assigns the tasks as follows:

  • Retain person assigned when restarting/resuming a Route: the same person who accepted the task is assigned the task when the route continues.
  • Reset to the original User Group(s) when restarting/resuming a Route: The task is reassigned to the user group and can be accepted by any one in that user group.

When all tasks are completed, the system changes the route status to Finished and notifies you that the route is complete. If a person rejects the task, the route is stopped and the system notifies you by email. The system does not route the files to anyone else until you resume the route. See Processing Rejected or Stopped Routes.