A route defines the sequence in which operators at different levels of technical support process requests of a specific type and priority. For example, requests with the same priority can be processed along different routes depending on the specified client.
At each stage, a separate standard applies to response time, solution discovery, and approval, known as OLA.
Let's look at how to configure a route.
Step 1. Create a route
To define the request processing sequence:
- Go to Service Desk > Routes and click + Route in the upper right corner of the page.
- Fill in the fields:

- Name*. Enter the route name.
- Activation criteria*. Select the criteria for applying this route to requests:
- By priority and type. Requests of a specific type and priority will be processed along this route. Specify the request type and priority level.
- By rule. The route will apply to requests whose parameters match a request processing rule. Create a rule or select a record from SD Rules > Rules.
- Processing method*. Specify how the request progresses through the route:
- Request. The request moves sequentially from one stage to the next.
- Task. Each stage of request processing can be split into multiple subtasks, and you can move to a new stage without waiting for the previous one to finish.
- Create new requests. At each stage, child requests are automatically created for the main request. When all child requests are closed, the parent request will be marked as completed.
- Requester for child requests. This field is available when the route processing method is set to Create new request. It allows you to specify the requester for child requests, i.e. the user who submitted the request. This user can receive notifications about the progress of request processing if you enable notifications in Service Desk settings.
Choose who should be notified about the progress of child requests: the assignee of the parent request, the requester of the parent request, a customer from the External Users directory, or an employee from the Internal Users directory.
- On request completion. If you selected Task or Create new requests as the processing method, when work at a specific stage is completed, the request will automatically move to the next step.
For the Request execution method, select how the request will be transitioned between stages:- Next Stage. The request will be automatically assigned to the next support group.
- Complete Manually. The operator manually changes the support group on the request page to move it to the next stage of work.
- OLA. If you selected Completion as the request completion outcome, specify the OLA standard to be used when manually moving the request between route stages.
Step 2: Define the route stages for request processing
After configuring the activation criteria and route processing method, add the route's individual steps, called stages.
- Click + New Stage. List the request processing stages and, depending on the execution method selected earlier:

- Request and Task. Specify OLA standards for each step.
- Create new requests. Specify the service whose OLA and SLA standards will apply to the child request at this stage, and select how problem data will be passed to the child request:
- Request. Information about the request subject, description, etc. will be automatically taken from the parent request.
- Route. Enter the subject and text for the future child request, and attach additional files.
- For the Create new requests and Task processing methods, you can divide a stage into multiple steps—called substages:
- With the Create new request processing method, these substages are child requests, each with its own assignee and response and resolution targets
- With the Task execution method, substages are separate tasks, each with its own assignee and the OLA targets you selected earlier.
All substages within a single stage start in parallel. By default, the Expect completion option is enabled for each substage. This setting determines which substages must be completed before the route can move to the next stage.
Example of expecting substage completion
To set this up, enable Expect completion for the Equipment Order substage and disable it for asset registration.. |
- You can also configure a stage to run only when specific conditions are met. In the Activation condition field, select an existing item from the SD Rules > Rules workspace or create a new rule. If a request does not match the rule's condition, the stage is skipped.
For example, an On-site Specialist Visit stage might trigger only for requests with the Incident type, high priority, and high urgency. - You can change the order of stages. To do this, hold the
icon and drag the stage up or down on the form.
To delete a stage, click the trash bin icon. - Save the settings.
The new route item will appear in the app. It will also be displayed on the request page on the OLA Stages and OLA Gantt tabs.