Bi-directional integration using single custom table for Incident, Problem and Change
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sunday
Hi Team,
I am working on a real-time integration use case and need your guidance on the best way to design it.
In the target instance, I have created one custom table which contains all the common fields of Incident, Problem and Change, along with some important table-specific fields. This custom table is acting like a unified repository.
Requirement is as below:
• When an Incident is created in the source instance, a record should be created in the target custom table and only Incident related fields should be populated.
• When a Problem is created in the source instance, it should create a record in the same custom table and populate only Problem related fields.
• When a Change is created in the source instance, it should populate only Change related fields in that custom table.
This integration should also work in reverse:
• If a record is created in the target custom table (based on whether it is Incident, Problem or Change type), the corresponding record should be created in the source instance.
We are planning this as a bi-directional integration, so we also need:
• Correlation ID to link source and target records
• Loop prevention logic
• Table identification (to know whether the record belongs to Incident / Problem / Change)
• Proper field mapping per table
• Error handling and retry mechanism
I would like to know the best practice approach for this design using Scripted REST APIs / IntegrationHub / REST Messages / Business Rules or Flow Designer.
If anyone has implemented a similar “single custom table acting as a hub for multiple task tables” kind of integration, your inputs or reference patterns would be really helpful.
