Ebonding is the integration of ServiceNow instance with ServiceNow instance itself, and it is generally done on modules like Incident, Change, Problem, etc. Doing ebonding includes a bit of scripting and debugging. Ebonding can be perfomed through various way like Scripted Rest apis, Table apis and Import set apis.
Using the Import set apis have some advantages over the others:
- Can use source script for a field in transform map for scripting like to map a choice field having different values of choice in both the instance.
- It is very helpful for debugging as we can see the data recieved for all the fields from other snow instance in the related links "input rows" in Inbound Web Service
- You can find the error message also in the related links "Import Sets" in Inbound Web Service while receiving data from other snow instances.
- Want to write an On Before Script ? Transform Script is the place for you.
All Configuration which will be needed for perform the ebonding :-
- Rest Message - Create a rest message and add the endpoints of the 2nd instance. Create an auth profile with itil and rest api explorer roles and add it to the basic auth profile in the authentication tab. Add the HTTP methods for the integration of respective modules.
- Business Rule - Create an After BR to send the payload to other instances via rest message. Might need to create a separate BR for passing the update payload to the other end. executeAsync() can be used to make the call asynchronously and it also gets ECC queue enabled where you can see the outbound payload sent logs and response recieved from other instance if any.
- Inbound Web Service - Create an inbound web service and add the table for which you want to ebond with the other instance. Add the fields which are required for ebonding and map them with the help of transform map. Note: Set a unique field as Coalesce "True" so that the update can be mapped to the same record. (Ex: Number / Correlation Display).
Mark Helpful(👍), if it added any value to you.
