...
Parameter | Description | Sample |
---|
snow_catalog_sys_ids
| A comma separated list of sys_ids . You can define the list of catalogs that you want to use. | snow_catalog_sys_ids = bdf16c2edb*******386f3731d9619f5, d5f4be1*******40cfdefda41d9619b9
|
snow_sys_class_name_to_page
| Contains the mapping of sys classes to the related portal page. It is a comma separated list of <sys_class_name>:<portal page name> . This is used for building the catalog item URLS (or have the URLs point to the Portal) | snow_sys_class_name_to_page = hardware_cat_item:device, kb_knowledge:kb_article, sc_cat_item_guide:sc_cat_item_guide
| snow_sys_class_name_to_ticket_id
| Contains the mapping of sys classes to the related ticket ID prefixes. It is a comma separated list of <sys_class_name>:<ticket id prefix> . This is used to get sys class by ticket ID prefix. | snow_sys_class_name_to_ticket_id = incident:INC, sc_request:REQ
|
snow_request_sys_class_names
| Specify sys_class_names of your request tables to manage requests. When you create a request, the the first table from the list is used; when you manage your requests (ask to display the complete list of requests), all the requests from all the tables are displayed. | snow_request_sys_class_names = sc_request, change_request
|
snow_sc_request_filter
| Specify sysparm_query filters using the Snow Glide format you want to use for getting requests from each request sys_class_name in the format: snow_<request sys_class_name>_filter . In addition to the standard syntax supported in Snow, you may use the special keyword {user_sys_id} that would be replaced by the invoker user sys_id. | snow_sc_request_filter = active=true^requested_for={user_sys_id}
|
...
In the chat, click the Quick Ticket Management button, then select List my tickets. The bot displays the complete list of tickets (both incidents and requests) with the current status.
All users tickets from tables defined in snow_request_sys_class_names
and snow_incident_sys_class_names
will be queries, using the filters defined in the related variables. See the table of variables above.
Troubleshooting
If the ITSM configuration is invalid, the Healthcheck displays an error. In this case, follow the recommendations given in the error message.
If the dialog in the chat seems strange and you do not get expected replies, you can turn on the debugging. To do so, run the following command: #debug on
and repeat the scenario to see the details. When you have finished the debugging, you can turn off the debugging functionality by typing #debug off
.
...