Name |
The name assigned by the route creator. |
Scope |
Determines the members that can be assigned
tasks for the route. See The Scope of a Route for details. |
Template |
The name of the template used to
create the route, if any. To see information about the template, click
its name. See Route Template Properties. |
State |
Not Started, Started, Stopped, or Finished.
Not Started means you began creating the route but didn't start it yet,
so no tasks have been created yet. Only the route creator can access
Not Started routes. Started means the route has been started but not
all members have completed their tasks. Stopped means a route member
has rejected the route (chosen Reject for the task approval status) or
the route owner manually stopped it. Finished means all members have
completed their tasks for the route. |
Description |
The purpose or intent of the route. |
Owner |
The person who created the route. |
Originated |
The date the route was created.
If the route was not started immediately, this could be different from
the date and time the route was started. |
Route Base Purpose |
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.
|
Route Completion Action |
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. If this
option is selected, the system automatically promotes the object when
the route is completed, assuming no other routes or requirements are
blocking promotion. The route owner is also notified of the route completion.
|
Auto Stop on Rejection |
Determines what happens
when a task in the route is rejected:
- Immediate. The route stops immediately.
- Deferred. The route stops after other tasks
at the current level are completed or rejected.
|