Integrations using correlation_id

[rlatorre]

Looking for advise and best practices.

We have many integrations with other applications. Some of the standard designs for these integrations utilize the "correlation_id" field to link a ServiceNow record with one in another application. We are getting to a point where a single ServiceNow record might need to be linked to more than one external application.

An example work be a SN Incident is related to a SFDC case and a Jira Defect.

If you have experienced this how have you tackled the design?

[Chuck Tomasi · Accepted solution]

Hi Robert,

Any time you have a 1 to many relationship, I recommend a related list of records. This means you get to create the table with those related records. The fields MIGHT look something like this for your use case.

• Parent record - reference to incident, task, etc.
• Data source - string (SFDC, Jira, etc.)
• Data reference - similar to correlation ID... some way to keep track of the remote record ID

You don't necessarily need to display this related list to anyone, but the table will help you manage the relationships between the remote record(s) and the SN record.

Keep in mind if your design will need to reference multiple tables - e.g. CMDB records AND task based records. That might be a better use for a document ID field than a reference field.

[rlatorre]

Thank you!

[Chuck Tomasi]

Hi Robert. You are very welcome.

If I have answered your question, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.

If you are viewing this from the community inbox you will not see the correct answer button.   If so, please review How to Mark Answers Correct From Inbox View.

Thank you