Update ticket integration setting
Changes the fields you send and returns the full updated document.
Send only the fields you want to change, plus version with the num from your last read and a change_description. This is a JSON merge-patch: a field you leave out keeps its stored value, and every list or map you send replaces the stored one whole. The id goes in the URL; if you also send id in the body it must match.
Authentication
JWT bearer token authentication. Include the Configuration API key in the Authorization header as ‘Bearer <token>’.
Path parameters
The id of the ticket integration setting, as returned when it was created or listed.
Request
If true, this is the primary ticketing system. Only one configuration can be primary; setting this true unsets the previous primary.
Ticket types the assistant can poll for status checks and nudges. Allowed values: INCIDENT, REQUEST, REQUEST_ITEM, CALL, TASK, MISC, UNIVERSAL_REQUEST, HR_CASE.
Ticket types polled so that assistant skills such as status checks, access requests, forms and triage can act on them. Allowed values: INCIDENT, REQUEST, REQUEST_ITEM, CALL, TASK, MISC, UNIVERSAL_REQUEST, HR_CASE.
Ticket actions the bot performs by impersonating the user instead of acting on their behalf. Allowed values: ADD_COMMENT, REOPEN_TICKET, RESOLVE_TICKET.
Path of the service portal in the ticketing system, used to build links to portal pages (e.g. servicedesk/customer/portal).
Response
Connector for the ticketing system these settings describe. Cannot be changed after creation. ID of an existing connector (GET /configurations/v1alpha1/platform/connectors).
If true, this is the primary ticketing system. Only one configuration can be primary; setting this true unsets the previous primary.
Ticket types the assistant can poll for status checks and nudges. Allowed values: INCIDENT, REQUEST, REQUEST_ITEM, CALL, TASK, MISC, UNIVERSAL_REQUEST, HR_CASE.
Ticket types polled so that assistant skills such as status checks, access requests, forms and triage can act on them. Allowed values: INCIDENT, REQUEST, REQUEST_ITEM, CALL, TASK, MISC, UNIVERSAL_REQUEST, HR_CASE.
Ticket actions the bot performs by impersonating the user instead of acting on their behalf. Allowed values: ADD_COMMENT, REOPEN_TICKET, RESOLVE_TICKET.
Path of the service portal in the ticketing system, used to build links to portal pages (e.g. servicedesk/customer/portal).