ServiceBridge Reote Task - how to set the CorrelationID of the Instance which triggered the sync

[Community Alums]

Let's say I have a RTD which will trigger a Remote Task on the Consumer instance when an incident is assigned to the "Network Support" group, and task will flow to the Provider instance and create a corresponding case.

By mapping the Incident Number, we can easily set the Incident Number as the Correlation ID on the Case.
But, until an update is triggered the opposite direction Case --> Incident, the incident will have an empty Correlation ID. This is problematic for us as the Customer likes to have this reference to 1) Know the integration has worked and 2) Have the Provider's identifier for any email/phone call conversations. 

With a REST integration with Consumer Creating a Case, you could get a Response back from the Provider with the bonded record number, but this concept doesn't appear to exist in ServiceBridge.

What would ServiceNow recommend is the best practice at point of bonding for the initiator to get the correlation ID value?

[Kenny Caldwell]

Hi ChrisT2,

With the latest patch release of Service Bridge for Providers v2.055 and Service Bridge for Consumers v2.055 remote task definition outbound mappings get returned to the source instance after insert in the target instance.

[VanGoghJoe1]

@Kenny Caldwell Can you elaborate on where those return values are seen in the source instance?  I upgraded to 2.0.55 on both sides and republished the remote task definition, but I still don't see inbound vars in the source remote task until a update initiated from the target instance is made to the parent task.  

[BobbyNow]

Please ensure you are creating new tasks to test this. This logic is only valid when the task is initially inserted. If you are reusing an existing task, it will find the matching sys_id on the other side and attach it to the Remote Task.

[Community Alums]

Sorry @BobbyNow can you provide an example with screenshots? See below, where Provider Case triggered a sync to Consumer Incident Task. This is a new task for integration, not existing.
The remote task on the provider side [sn_sb_pro_remote_task] looks like this and viewing the XML, there is no data with any response data from the consumer i.e. to give us the Incident Task Number that was created. 

In this example, you can't see the inbound vars (including the incident task number) until a separate update is initiated on the consumer incident task -  and this could be some time after the initial bonding