Correlation id and Correlation Display ??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2014 02:03 AM
What are these Correlation id and Correlation Display fields for?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2014 06:12 AM
These fields are typically used for Integration purposes. You will often store a corresponding third party record ID in the correlation ID field. The correlation Display field can contain a free-form descriptive label of what third party system is replicating or tied to this record.
For example, if you are tying incident records to a third party ticketing system when they are created within ServiceNow, the corresponding ticket ID from the third party would be stored in the correlation ID field. You could also set the correlation display field to be "JIRA", or "REMEDY", or whatever you want to indicate the third party system using this ticket.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2014 10:47 AM
is correlation id available on all extended tables? if source sytem id is string but length is only 32 , is it possible to map the external system's unique id in correlation id field?
is it possible to mass update the correlationid field with values from external system without triggering any business rules?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2014 02:12 PM
Yes, correlation_id is defined on the Task table so any subclasses will have the field. The maximum length is 100 so it will fit.
Check out the following 2 GlideRecord methods for updating a record but not changing the system fields nor run Business Rules:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2014 10:43 AM
how are these IDs handled when there are more than one integration, but involving two different tables.
In our scenario we are using correlation id on incident table to store external Service manager incident # in correlation id on incident table.
But we have to create another integration where CMDB excel extracts with unique CMDB Id from external vendor needs to be mapped to a field on cmdb_ci and cmdb_appl tables. so both these table have correlation id.
But correlation id in these two cmdb tables be used ?
2.will this still cause any data, key integrity issues even though they are on different tables because the Service manager only uses correlation id on incident table not cmdb table? .
3. Is it better to create a custom field on these tables .What is the best practice here , using correlationid and correlation display in conjunction or totally creating custom fields in cmdb tables to store the new integration unique id. Moderations , implementation specialists any quick suggestion here ?
