About Route Templates

A route template contains the frequently reused components of a route,

The route template includes items such as the route description, members, task order, and instructions. The components of a route that are typically unique for each route—the route name, the content being routed, and the access levels assigned to route members—are not saved in the template.

Route templates can be saved with no members and therefore no task assignees. If you create a route based on a template that has no members, you have to add members and assign tasks before starting the route. If the route template has members, some tasks may still be unassigned and you have to assign these tasks before starting the route.

When defining a linked series of routes, you can only link routes defined with a Route Base Purpose of Standard. You cannot link routes defined for Approval or Review.

The route template includes a "Start Route On Completion" field that lets you select another route template. When the current route completes, a route created from the linked template is started. All content from the first route is included in the subsequent route. The person who owns the first route is defined as the owner for the subsequent route. Route creators can user 3DNotification to choose to be notified when a linked route is started.

You can link any number of route templates together as required to define a workflow. You can only link route templates, you cannot link routes that are not created from a route template.

For each route template that includes a following route, you can define the Route Completion Action for that following route. For example, if a route is part of a series of routes, you can choose Notify Only so that the route owner will be notified when that route completes and the next route begins. For the second to last route in the series, you can choose Promote Connected Objects so that when the last route in the series is completed, the connected objects are promoted.

If an error occurs in a route or any approval task in a route is rejected, the linked route is not created. If a task in the linked route is assigned to a user group and has "Select User(s) from User Group(s)" specified, then the subsequent route will be created but will not be started until a specific user is selected.