A service request can be created/submitted in three ways:
- from the Service Catalog via the Self-Service Portal
- via the agent interface
- from a user query
Via the Self-Service Portal
This procedure implies that it is performed by an end-user.
From the Self-Service Portal, you can submit a service request by selecting a respective, pre-defined request from the Service Catalog. To do so, complete the following steps:
- Navigate to your Portal main page.
- Click the Service Catalog card.
- From the respective category, select the required request and fill in the fields.
- Click Submit Form.
As a result, the new service request will be created in the Registered state.
You can track the work process on the My Tickets page. To open the record of the service request, complete the following steps:
- In the header, navigate to Cabinet → My Tickets.
- Click My Service Requests on the left.
- Check the state of the created request.
Via the agent interface
This procedure implies that it is performed by a user with the ITSM_agent role.
To create a service request via the agent interface, complete the following steps:
Navigate to Service Request Management → New.
Fill in the fields.
Click Save or Save and Exit to apply the changes.
You can copy the record number, title, and link via the hamburger menu. To do so, click Generate Link.
New Service Request form fields
Field | Mandatory | Description |
|---|---|---|
| General tab | ||
| State | Y | This field is populated automatically with the Registered state when the request is being created. To learn about the other states, see Process Service Requests. |
Impact | Y | Measure the effect that the service request may cause on the business processes. See the Priority Management article to learn more. |
Urgency | Y | Specify the urgency of the request. Typically, it is evaluated based on the time remaining until the issue impacts the business. See the Priority Management article to learn more. |
Priority | N | Priority is a function of impact and urgency. It identifies the importance of a request. See the Priority Management article to learn more. |
Assignment Group | Y | Specify a group responsible to work on the request. When a service request is assigned to a group, the Assigned User field becomes non-mandatory. There is a dependency between the Assigned User and Assignment Group fields. Refer to the Task Auto Assignment article to learn more. |
Assigned User | Y | Specify a person responsible to work on the request. When a service request is assigned to a user, the Assignment Group field becomes non-mandatory. There is a dependency between the Assigned User and Assignment Group fields. Refer to the Task Auto Assignment article to learn more. |
Subject | Y | Add a brief description of the request. After saving, the field is hidden on the form. |
Description | N | Add a detailed description of the request. |
Related CIs | N | Specify service-related configuration items affected by this service request. |
Caller | Y | Specify the request originator. |
Company | N | Specify the company to which the request is related. |
Service | Y | Specify the service affected by this service request. |
| Attention Required | N | Select this checkbox to notify the line manager of the assigned group/assigned user. |
| Activity Feed | ||
| This section appears after the request is saved. | ||
| Additional Comments | N | Add some comments with information about the request. |
| Work Notes | N | Add work notes that may be useful. |
| Related Records tab | ||
| Use this tab to create relationships between service requests and other types of tasks. See Create Records Related to Service Requests to learn more. | ||
| Closure Information tab | ||
| This tab appears when the service request state is Completed. See Process Service Requests to learn more. | ||
| Followers List | ||
| This field is populated automatically with a list of users who follow the request for tracking the updates. | ||
