Page History
| HTML |
|---|
<style>
.release-box {
height: 30px;
width: 100px;
padding-top: 8px;
text-align: center;
border-radius: 5px;
font-weight: bold;
background-color: #8efeb3;
border-color: #FCE28A;
}
.release-box:hover {
cursor: hand;
cursor: pointer;
opacity: .9;
}
</style>
<meta name="robots" content="noindex">
<div class="release-box">
<a href="https://docs.perspectium.com/display/krypton" style="text-decoration: none; color: #FFFFFF; display: block;">
Krypton
</a>
</div> |
The Zendesk meshlet supports the following configuration directives listed below in additional to the general configurations supported by all ServiceBond meshlets For questions, contact Perspectium Support.
NOTE: Default values refer to the configuration's value if the configuration is not specified in the meshlet configuration file.
| Directive | Default Value | Required | Description | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
perspectium: meshlet: scheduler: pollingInterval: 180000 | 180000 | Yes | The time for the meshlet to wait in between polling for changes in Zendesk. This value is in milliseconds i.e. 180000 = 180 seconds (3 minutes).
| |||||||||||||||||
apiTokenAuth | false | No | Indicates whether you want to authenticate your Zendesk connection with an API token instead of basic authentication.
| |||||||||||||||||
| urlBase | Yes | The base portion of the Zendesk API URL. Since Zendesk includes the resources being interacted with as part of the URL (i.e. https://subdomain.zendesk.com/api/v2/tickets.json, https://subdomain.zendesk.com/api/v2/users.json, etc.), we separate the URL so we can easily add the different resources below.
| ||||||||||||||||||
| urlSuffix | Yes | The ending (suffix) for the Zendesk API URL. Usually this is .json for API URLs such as https://subdomain.zendesk.com/api/v2/tickets.json
| ||||||||||||||||||
| urlResources | Yes | The resources being interacted with through the API. Each resource should be listed out with a - and contain the following properties:
| ||||||||||||||||||
| defaultCreateDescription | New ticket from integration | No | Since Zendesk requires a description to be the first comment added, a default description to use if no description is specified when the meshlet receives a message from the other ITSM app like ServiceNow. This ensures the ticket is created successfully since it uses the default description as specified here if no description was specified in the incident coming from the other ITSM app.
| |||||||||||||||||
| defaultAttachmentComment | Attachment added to ticket | No | Zendesk requires attachments be added as part of a comment to the ticket. By default, the attachment is added with a comment Attachment added to ticket but you can use your own comment for when attachments are added into Zendesk by setting this configuration.
| |||||||||||||||||
| defaultCorrelateResponse | No | For when you configure ServiceNow to send back a .correlate message to Zendesk, this message can appear as a comment on the Zendesk ticket so those looking at the ticket in Zendesk will know the ticket was created in ServiceNow.
| ||||||||||||||||||
| correlationFieldId | Yes | The Zendesk Field ID of the Correlation ID custom field in Zendesk that holds the unique identifier in the other ITSM app being integrated with Zendesk i.e. the sys_id in ServiceNow. This field should be created as detailed here.
| ||||||||||||||||||
| correlationDisplayFieldId | No | The Zendesk Field ID of the Correlation Display custom field in Zendesk that holds the customer-facing identifier in the other ITSM app being integrated with Zendesk i.e. the number in ServiceNow. This field should be created as detailed here.
| ||||||||||||||||||
| startTime | Yes | The start time when the meshlet first runs to query for ticket changes from. That is, it looks for any tickets that have been changed (updated or inserted) since this time on first start. After the first run using this start time, the meshlet will only query for changes since the last time it ran. This value should be entered in epoch time format in UTC/GMT time. See https://www.epochconverter.com/ to translate into this format. If this value is blank, it will query for all ticket changes when the meshlet first runs. For example, this will query for changes to tickets the first time the meshlet runs:
And this will query for all changes to tickets since 2022-08-09 1:38:42 AM (2022-08-08 6:38:42 PDT) the first time the meshlet runs:
| Yes | The Zendesk ID for the user entered in perspectium.auth.username. This field will be used to check for any updates in Zendesk made by this user ID so they can be skipped to avoid looping updates back and forth between Zendesk and other ITSM app being integrated.
| ||||||||||||||||
| historicalComments | true | No | For when a ticket in Zendesk triggers being integrated and whether or not we should get all the comments previously entered prior to the ticket triggering the integration. If true, all comments will be sent. If false, comments entered prior to the integration being triggered will not be sent.
| ticketPageSize | 1000 | No The number of tickets to query at a time. This value is to control performance so as to not slow down the meshlet and/or your Zendesk environment so as to not query for too many records at one time. If there are more tickets than the value specified here, it will grab it the next time when it queries for the next "page" (batch). 1000 is the maximum value allowed.
| ||||||||||||||
| notifyZendeskError | false | No | To enabling creating a new ticket in Zendesk when there is an error with Perspectium. This is useful when you want to trigger a notification in Zendesk for Perspectium errors. See notifications in Zendesk for more information.
| |||||||||||||||||
| defaultErrorMessage | Perspectium Error | No | Related to the notifyZendeskError configuration, the error message to display when creating a new ticket in Zendesk due to an error with Perspectium to trigger a notification. See notifications in Zendesk for more information.
| |||||||||||||||||
| ticketSleepTimer | 60000 | No | The time for the meshlet to wait ("sleep") before trying any new requests if it it reaches the results or rate limits to ensure the meshlet is not locked out of accessing the API. This value is in milliseconds i.e. 60000 = 60 seconds.
| |||||||||||||||||
| queryMethod | Yes | The method to query for changes in Zendesk for sharing out to the other ITSM app being integrated. Options are either search or cursor. If the method is search, the API will use the Search API to query for changes. Records will be queried based on any changes greater than the last query time along with any filter conditions specified in the query configuration below. The first time the meshlet runs, it will query for all changes since the meshlet first started. If you want to get all tickets, use either the cursor method or set the query string to have an older date.
If the method is cursor, each time records are queried, the API leaves a cursor where it last retrieved records from. On the next query, it will get all records since this last cursor. See cursor export for more information.
| ||||||||||||||||||
| query | Yes, if queryMethod is search | To This configuration only works if the queryMethod configuration is search. This allows you to specify query conditions for records that should be shared from Zendesk. This configuration only works if the queryMethod configuration is search. Valid formats for query conditions can be found as detailed at Search API and Support search reference.
If you include the updated or created condition in your query string, this will override the default check of looking for tickets that meet your condition(s) and were last updated since the last time the meshlet queried for changes. You can use the syntax as described in the Search API and Support search reference (spaces or +) for having multiple conditions together. For example, this query will find tickets updated since July 1, 2022 that have the dog tag:
| ||||||||||||||||||
| startTime | (blank) | No | This configuration only works if the queryMethod configuration is cursor. The start time when the meshlet first runs to query for ticket changes from. That is, it looks for any tickets that have been changed (updated or inserted) since this time on first start. After the first run using this start time, the meshlet will only query for changes since the last time it ran. This value should be entered in epoch time format in UTC/GMT time. See https://www.epochconverter.com/ to translate into this format. If this value is blank, it will query for all ticket changes when the meshlet first runs. For example, this will query for changes to tickets the first time the meshlet runs:
And this will query for all changes to tickets since 2022-08-09 1:38:42 AM (2022-08-08 6:38:42 PDT) the first time the meshlet runs:
| |||||||||||||||||
| ticketPageSize | 1000 | No | This configuration only works if the queryMethod configuration is cursor. This specifies the number of tickets to query at a time. This value is to control performance so as to not slow down the meshlet and/or your Zendesk environment so as to not query for too many records at one time. If there are more tickets than the value specified here, it will grab it the next time when it queries for the next "page" (batch). 1000 is the maximum value allowed.
|