The field should be created as Text field type and can have any display name and properties as desired. Image Added
Once you have created the field(s), note each field's Field ID as you will need those for configuration the meshlet. Image Added
This field ID will also be used in the Zendesk meshlet's mapping files for mapping records created/updated in the other ITSM app into the Common Incident format for mapping into Zendesk. For example, if you are mapping how to create tickets in Zendesk from ServiceNow, the mapping would look as follows:
Code Block |
---|
| {
"ticket": {
"comment": {
"body": "${JSON_ENCODE:$[XPATH:/common_incident/description]}"
},
"type": "ticket",
"priority": "${XPATH:/common_incident/priority}",
"status": "${XPATH:/common_incident/state}",
"subject": "${JSON_ENCODE:$[XPATH:/common_incident/short_description]}",
"custom_fields": [{"id": 7655609750043, "value": "${XPATH:/common_incident/sys_id}"}]
}
} |
You will notice the custom_fields section where the Correlation ID's field ID (7655609750043) is listed so it knows to update this field with the sys_id from ServiceNow. NOTE: You may need to refresh your browser to see the new custom field on the ticket form in the Zendesk UI.
|