Work-Around Fix : Outbound_Vars_Json is not received when Parent record inserted in remote systemTerminology : Remote Task Definition : Mentioned as RTD into this below KB from now on.Remote Task : Mentioned as RT into this KB below from now on. Problem Statement : In Service Bridge for Provider and Consumer application version more than or equal to 2.0.20, spontaneous outbound_vars_json is not flowing back because there is a design change from the service bridge side. The customer has configured RTD in outbound mapping to get back the parent task number as soon as the parent task record is created in the target/remote system. This is not happening. Service Bridge for Provider / Consumer Impacted Versions : sn_sb_pro : 2.0.20, 2.0.30 ... upto 2.1.30sn_sb_con : 2.0.20, 2.0.30 ... upto 2.1.30Expected to be fixed in Version in App (sn_sb_pro, sn_sb_con) : 2.2.0 and more Work-Around Procedure : In Provider (Installed PlugIn : sn_sb_pro) Instance :- STEP 1 : Apply the Update set attached here name : sys_remote_update_set_ba96af7293959210b15e39018bba108d.xml STEP 2 : Test by creating a Parent task from Consumer Success : If you get back the outbound_vars_json as soon as Parent task created in Provider Instance back and it's updated into Consumer Parent corresponding fields. Failure : Outbound_vars_json is not found in Transport Queue list for that Remote task, Please, check Remote task is updated to Status = connected. Check the All > System Log > log message starts with 'SNow-Pro-BR_001' which proves that BR hit or not In Consumer (Installed PlugIn : sn_sb_con) Instance :- STEP 1 : Apply the Update Set attached here name : sys_remote_update_set_c5a7cb72eb5d1e10ea03fde5bad0cd30.xml STEP 2 : Test this by creating a Parent task from Provider Success : If you get back the outbound_vars_json as soon as Parent task created in Consumer Instance back and it's updated into Provider Parent corresponding fields. Failure : Outbound_vars_json is not found in Transport Queue list for that Remote task, Please, check Remote task is updated to Status = connected. Check the All > System Log > log message starts with 'SNow-Con-BR_001' which proves that BR hit or not <Important> Before Upgrade to version 2.0.40 and more release : You have to follow any ONE of the two options mentioned below before upgrade to version 2.0.40 or more next app (sn_sb_pro / sn_sb_con) release. Option 1 : You can disable (Set Active flag to false) this Business Rule created by the Update Set given above because that is no more needed in Provider and Consumer instance after successful upgrade. Option 2 : Back out the above update sets which can drop the Business Rules created. Permanent Fix : Please, check below for more details of the permanent fix availability. This is been fixed via 2 phases, initial fix also have some intermittent issue which is below - // In API below SBRemoteTaskUtil()._setRemoteTaskOutboundJSON() { .. ... remoteTaskGR.parent.getRefRecord(); // This getRefRecord() is failing on customer side ... ... } Now, this also fixed by PRB1847705 in release >= 2.2.0 PRB : PRB1817771PRB1847705 (DEF0627617) - https://support.servicenow.com/problem.do?sys_id=c70f7062931f9210101833527cba1051 Problem Statement : In Service Bridge for Provider and Consumer application version more than or equal to 2.0.55, outbound_vars_json is empty at consumer end due to sys_class_name is empty. Service Bridge for Provider / Consumer Impacted Versions : sn_sb_con : 2.0.55Expected to be fixed in Version in App (sn_sb_pro, sn_sb_con) : 2.2.0 and more Work-Around Procedure : In Consumer (Installed PlugIn : sn_sb_con) Instance :- STEP 1 : Upload the XML attached here name : sys_script_f6ae047deb95d610ea03fde5bad0cd8e.xml STEP 2 : Test this by creating a Parent task from Provider Success : If you see that outbound_vars_json is not empty as soon as Remote Task is created at Consumer due to Transport Queue updation. Failure : Outbound_vars_json is empty in the Remote task at Consumer end, Please, check Remote task is updated to Status = connected. Check the All > System Log > log message starts with 'SNow-Con-BR_001' which proves that BR hit or not <Important> Before Upgrade to version 2.0.55 and more release : You have to follow any ONE of the two options mentioned below before upgrade to version 2.0.55 or more next app (sn_sb_pro / sn_sb_con) release. Option 1 : You can disable (Set Active flag to false) this Business Rule created by the Update Set given above because that is no more needed in Provider and Consumer instance after successful upgrade. Option 2 : Back out the above update sets which can drop the Business Rules created. Permanent Fix : Please, check below for more details of the permanent fix availability. PRB : PRB1847705 (DEF0627617) - https://support.servicenow.com/problem.do?sys_id=c70f7062931f9210101833527cba1051The permanent fix also clear out the BRs created by this Work-Around executed into the instances