Introduction

Routes are collections of tasks assigned to one or more people in the organization. Routes can be used to provide information on actions required as part of an approval process; for example an approval of a document. In the case of a Change Action to define the tasks and instructions required to approve that Change Action. Upon completion of the route, the Change Action will then be completed and subsequently, the “In Work” items in the ‘Realized Changes’ would be promoted to “Released” lifecycle maturity state.

Route template

In order to enable the usage of a route in the approval process of the Change Action, route templates should be created and released. The “Route Base Purpose” attribute of the route template should be of type “Approval”:

To release the route template, use the “Set to Released” option:

Approval Route in the Change Action:

To add a route in the list of approvers in the Change Action, open the “Members” list and add the new route template into the list of “Approver”:

Note that you can add additional “direct” members as approvers.

Change Action – Approvals:

As long as the Change Action is not yet in the state of “In Approval”, the list of “Approvals” will be empty, to indicate that the approval process has not yet started:

Setting the Maturity state of the Change Action to “In Approval” will initiate the process:

The “Approvals” tab contains now a new route that contains all the tasks that are required to approve the Change Action:

• Tasks created for the direct members (added in the beginning of the route)
• Tasks created from the route template (note: this is a new route which is generated from the route template, and can be edited if needed, see below)

You can use the “Edit” option of this new route in order to better fit it for the purpose of this specific Change Action (delete tasks, add new ones, modify members etc.)