Previous Document Next Document Show Current Location in Contents Common Components Help AEF Help

Consequences of Creating a Route Based on a Route Template

When you create a route, you have the option of basing it on a Enterprise route template or a route template created previously by you. A route template contains the components of a route that are frequently reused, such as the route description, route members, and task definitions. Content is not included in a route template. Basing a route on a route template can speed up the route creation process because the system pre-fills the member and task information for you.

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'll 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'll have to assign these tasks before starting the route.

In Team Central, if the template is based on a route that has a scope item defined (a workspace, for example) and it contains members who do not have at least Basic access to the scope item, they are not included in the route. Any tasks these people are assigned are removed from the route.

The route template controls the amount of editing that can be performed on the task list for routes created from the template. A route template can be defined to allow one of the following four levels of editing. These edit levels control whether the person who creates routes from the template can add and remove tasks, edit the task names, and edit the task orders. The pages that let you define the tasks for a route indicate the tasks that come from the template with a (t).

Previous Document Next Document Show Current Location in Contents

Last updated: 04/20/04 14:50:42