What Is ServiceNow Integration?
ServiceNow integration extends your IT system’s performance via connecting disparate practical areas of your enterprise by the ServiceNow platform. ServiceNow lets you combine with SaaS, IaaS, ERP systems, on-premises applications, legacy systems, and databases.
Design the Flow
The diagram assumes occasion 1 and occasion two as dev1.service-now.com and dev2.service-now.com respectively. The method entails one-way verbal exchange from dev1 to dev2, which operates on Create and Update.
Flow 1: Start > Create Incident in dev1 > Copy small print to dev2 > Create Incident in dev2 > End
Flow 2: Start > Update Incident in dev1 > Copy important points to dev2 with reference to already current file > Update Incident in dev2 > End
Note: Both situations are in parallel connection earlier than we start this integration, which means there is no cloud-based, place-based total connection inside any routing mechanism.
Configure the Endpoint URL and Authentication
This will be finished in the ‘System Web Services > Outbound > REST Message or SOAP Message’ of the ServiceNow dev1 instance. The Endpoint URL relies upon the REST or SOAP approach of Integration to figure out the flow. Authentication will be protected inside the REST Message or in the HTTP Method. Details are proved in Step 5.
HTTP Methods allowed for operations are POST (for developing a file in dev2), PUT (update), GET (retrieve/read) and DELETE (delete). We reflect on the consideration of POST and PUT techniques in this project.
Explore the verbal exchange channel
The conversation channel we selected is one way from dev1 occasion to dev2 occasion to both create or replace incident records. This manner needs an Outbound Web Service to be enabled at supply occasion i.e., dev1 instance. There is no want for an inbound message at dev2 as ServiceNow handles the complexity here.
MID Server Usage
As this is a demo project, we have now not configured any MID Server however involving MID will assure a tightly closed connection for stay environments. If we do consist of this, then the attachment is made inside REST/SOAP Message shape as a reference discipline linked to MID Server.
Enter Into Gologica On ServiceNow Integration, Join Now
REST Message (or) SOAP Message
We gonna be the usage of RESTful offerings in our project, the method for this will be proven in the screenshots below.
- Create a new REST Message and add the important points as shown. Replace ‘dev2’ textual content in the Endpoint URL with your occasion name. Create a new ‘Basic AUTH profile’ which holds the credentials of the dev2 instance, as a pre-step for this profile, create a new person profile in dev2 occasion for managing REST primarily based incidents from dev1 exclusively.
- Dev2 Instance User Profile should have ‘web_service_admin’ and ‘’rest_service’ roles as a phase of REST integration access. Make certain you get the right of entry to the application/table (in our case it is Incident Management/incident of dev2 instance) which has ACLs that permit creating and writing operations. As ACLs take extra priority than the integration role, you have to add indispensable roles for having access to the incident desk right here (in our case we do not want any exterior function to create or write to the incident table)
Also Refer: ServiceNow Admin Training
- HTTP Method – POST: (PUT is no longer proven here, you can configure the identical way with little variations which if required we can do in the comments)
Note the Content displayed in the POST operation – {“short_description”:”${short_desc}”}. We are simply passing one parameter for this demo.
Click on Preview Script Usage in the associated hyperlink below the identical structure as shown:
Read Also: ServiceNow Training
This shows the convenient script that we want to insert in our subsequent step – Business Rule
Before shifting on to Business Rule, we have to create a brief description discipline in the variable substitution beneath POST HTTP Method for REST Message, simply observe as proven below. You can supply a default cost to verify and click on the Test hyperlink beneath which creates a document in Dev2 occasion with default cost on the quick description that you chose. In the subsequent step, we make this default fee to the dynamic quick description from the dev1 instance.
Use of Script Include: (Instead we use a Business Rule)
There are no conditional or filtering operations we want as a section of occasion to occasion integration. ServiceNow lower backstop desk schema and API similarities right here get rid of away the complexities. However, we do want to affirm matters when we combine them with any third-birthday celebration tool/platform.
Business Rule Usage:
Write a Business Rule as proven beneath on the incident table, click Advanced if you do not locate each area as shown.
Go to the Advanced tab and reproduction the script that you generated above Step 6. We do want to edit the script here.
Deciding on the Message structure
For the message structure, we suggest the facts syntax be used whilst transferring records from dev1 to dev2. As stated each case has a comparable gadget configuration or residence and subsequently the general strategies of message shape can be undertaken. For REST the structure would be JSON (JavaScript Object Notation) and for SOAP it is XML(Extensible Markup Language). In our case, this would be JSON Structure and the default REST Message’s HTTP Header would be ‘application/JSON.
Define Parameters, attributes, or fields
There is a want for a special discipline that will be used at dev1 occasion to make positive the subject exists in dev2. What we imply right here is, say Correlation ID is a discipline in dev1 and this holds the fee of SYS_ID from dev2 for each newly created incident in dev2. Also, if we have been to replace any file we use this Correlation ID from dev1 and search in the dev2 instance, if located then that specific document will be updated.
Dev1 occasion Incident structure fields – notify Correlation ID field, populating this area is completed dynamically from a Business Rule.
Result Screenshots
Dev1 occasion is in Madrid launch and Dev2 in Kingston. Note the incident numbers for every occasion are different. Also, as trace purchaser situations are all linked to one source, subsequently we do now not want integration in case there is a requirement to replica records, as a substitute we can request for a System Clone in that case.
Dev1 Incident Details:
Dev2 Incident Details:
Conclusion
Advanced workflows usually consist of several varied applications, platforms, and information. Integration Hub empowers engineers, IT generalists, and technique examiners to stretch outflow in the Flow Designer to any outsider’s help and efficaciously make end‑end digital work processes. Organizations can besides a good deal of a stretch grow their capacities via using the integrations and giving superb consumer self-administration portal for customer assistance. These integrations will additionally allow the customers to cope with issues via availing a few administrations recognized with data.
Enroll in Gologica Online Training right now and enjoy the benefits. I hope that this post has helped you improve your ServiceNow Integration knowledge.