Creating Routes with Only Basic Information

You can create a route by entering only basic information for it. After creating the route, you must define content, member access, and tasks before you can start the route.

For an approval route, if you choose "Promote Connected Object" for the"Route Completion Action," the connected object is promoted when the approvals are done, even if the users who approved the tasks do not have promote access. However, the route owner must have promote access for the content.

To quickly add tasks and assignees to a route, you can base it on a route template. After creating a route, you cannot change the template it is based on. For more information, see Routes Based on Route Templates.

For instructions on using the Route wizard to define all components of the route when you create it, see Creating Routes Using a Wizard. For more information, see About Routes.

Required access roles: If you have access to an object, you can create routes for it. For baseline behavior, you must have at least the Contributor access role.

  1. To create the route from thetop bar, click > Routes > Create Route.

    To create the route from the Routes Summary page:

    1. Open the Routes Summary page. For more information, see Routes Page and Routes Summary Page.
    2. Click Create Route .

    Or, to specify the object for the route:

    1. Access the routes category for the required item.
    2. From the page toolbar or Actions menu, click Create Route .

    For details, see Routes Page and Routes Summary Page.

  2. Enter the Name you want to use for the new route, or select the Autoname check box to have the system assign a name. When a route is automatically named, the system assigns a prefix and a sequential number for the name, such as R-000305.
  3. For subroutes that you are creating to complete another route's task, use the Visible to Parent Route Owner options to choose whether you want the subroute to be shown to people who can access the parent route. This includes the parent route owner, all members of the parent route, and the Bookmark Root owner.

    • No. Others cannot see the subroute
    • Yes. Others can see the subroute.

    These options are only shown for a subroute.

  4. If you want to base the route on a template, click the Template to search for and select a template. If a route template has multiple revisions, only the latest active template can be selected.
  5. Enter a Description that indicates the route's purpose.

    If you base the route on an existing template, the description is already entered. You can edit it as required.

  6. Select the Route Base Purpose, which determines the kind of tasks included in the route.

    • Standard. The route can include tasks that require the assignee's approval or comment or tasks intended only for notification or information.
    • Approval. The route includes only tasks that require the assignee's approval.
    • Review. The route includes only tasks that require the assignee's comment.

  7. Choose the route's Scope: All or Organization. You can click to choose a specific Bookmark Root or Bookmark. For more information, see Scope of a Route.
  8. Select a Route Completion Action, which determines the events that will occur when the route is complete:

    • Notify Route Owner. When the route is complete (all tasks are completed), the system sends a notification to the route owner.
    • Promote Connected Object. This option is for routes with content for which the route owner has defined lifecycle block states. When selected, the system automatically promotes the object when the route is completed if no other routes or requirements block promotion and the route owner has promote access to the connected objects. The route owner is also notified of the route completion.

      If you have already added content to the route, you can only select this option if the route owner has promote access to that object.

  9. Select a value for Auto Stop on Rejection to define what happens when a task in the route is rejected:

    • Immediate. The route stops immediately.
    • Deferred. The route stops after other tasks at the same level are completed or rejected.

  10. Select a value for Revert User Group(s) Assignment to define what happens when restarting or resuming a route when a person from a user group has accepted a task:

    • 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.

  11. Click Done.
  12. The Properties page for the new route opens. Before starting the route, you must add content, add members and assign accesses, and define tasks using these procedures:

    When ready to start the route, follow the instructions in Starting or Resuming a Route.