BR's are server side scripts that executes on record insertion, updation, deletion/quering, they are mostly use in SN integrations to allow automation and data processing. @Ravi, please correct me, if wrong. Bdw Thanks for such an amazing explanation of E-bonding integration.
Amazing, the more I understand the process and configuration steps. I have realized this is like SQL Stored Procedure having parameters to be saved in another DB. COOL WOW thank you so much for explaining it clearly every bit of it.
You are awesome in explaining and doing the demo, even the topic is new for me I can easily follow and grasp what you are teaching. Keep it up, we are learning a lot from you, thank you.
massive thank you for this video. for the next video i will do the following scenario: you have now integrated 2 servicenow instances. now let's make instance 1 able to receive updates from instance 2 about the incident we have created on instance 2.
Thank you for your valuable videos,so much content and information in your videos. Also request you to share some sample resumes for servicenow admin and developer this could really help us
Hi Ravi, Thanks a lot for your wonderful videos, your way of explaining makes me understand well. I am wondering if two instances of different versions (Vancouver and Washington DC) of ServiceNow could be integrated.
Hi Ravi I have been going through your integration videos and I liked the the way you explain Can you please create videos on implementing certain retrictions on servicenow field during integration For example - restricting certain value to be updated in field on inbound web services.
@ravi, thanks for creating such amazing videos on outbond webservices. Request you to please make one video on PUT or PATCH method with dynamic update an instance-1 to instance-2.
Thank You so much Ravi...You are such a brilliant Teacher... I have a little problem....the incident is getting created in target instance but it is not populating caller and category...please help me ASAP!!
Business rules are triggered by events such as record insert, update, or delete, making them suitable for scenarios where you want to automate actions based on these events.
What is even the actual real world application of e-bonding? Why would anyone want to create a duplicate incident in another instance? Thanks in advance if you would clarify this.
Its because.. there are multiple servicenow instance exist in nature… Like one development instance where developers will develop something… Test instance will testing team will test and production will live data is tested.. so its required
@@learnservicenowwithravi Thanks for replying. So the way I understand it, it is because the client requires to keep their dev/test/temp instances in sync with prod instance. Is it correct?
@learnservicenowwithravi and @ vishalpallikonda3641 There are some other use cases as well, where the client and the service provider has two different instances, but the client want to send the incidents to the service provider's instance to work up on and drive them to closure where most of the Operations teams are from service provider's organisation. They want some real time updates to see as well like work notes and state. They will be created with a correlation id
When I'm Doing Ebonding integration on that Before BR and operation is insert, then I have created incident its creating multiple incidents, What is the reason?
could you please create a video on How to update incidents of intance 1 if same incidents are updates on instance 2? for example for INC001 short description is changed and for INC002 category is changed and We nee to synch those changes to same records on Instance 2 How can we achieve this please give me some guidance Thanks
@@learnservicenowwithravi thanks but I want to update same records on instance 1 if any changes happened to records in instance 2 So my question is How can we get updates of mutiplae records ..in rest message module you showed us for only 1 record by adding sys_id of one incident so what if I want to get updates of multiple records based on conditions where should I write that logic ?
Hi Ravi, I am doing the exact same thing and it is creating the incident in the other instance but the variables are not captured, only the incident is created with blank data, also i can't see logs in my other instance where i am developing Rest message, please help
When I am creating a new Post method it throws an error "401" but when i check my connection with default "get" methos connection is "good" dont know how to resolve this can you please help me in this.
Hi Ravi, in one of the interview they have asked me why u need sn to sn integration in real time ? I said incidents but they are not satisfied with the answer. Integrating Servicenow with Servicenow in real time why ? Can u please tell me why we want this in real time
I am trying to integrate two instances as shown in the video connection is successful but the incident created on other instance is not taking the short description value mentioned in the incident created on source instance..any help??
not running for me when i click on preview script usage i get the code same as you but when i paste it in business rule as done by you my color coding is red i am not getting why everthing is same as you shown i am pasting the code below please help :- the color for (current,previous) is fully white its not blue as it should be similarly for ('ServiceNowEbonding', 'Create an Incident');&('details', 'test123'); the color is red and not blue thats why its not executing till the Test part where we click on test manually its working but not the after part (function executeRule(current, previous /*null when async*/) { var r = new sn_ws.RESTMessageV2('ServiceNowEbonding', 'Create an Incident'); r.setStringParameterNoEscape('details', 'test123'); var response = r.execute(); var responseBody = response.getBody(); var httpStatus = response.getStatusCode(); })(current, previous);
While creating incident in source instance, I have mentioned caller_id and category, they are reference and string field..but when I check same.incident in target instance, i do not find caller id and for category, it's always taking inquiry/help, for whatever the value I am providing in source..I have followed same to same.instructructions, can you tell me what may be the issue
