No Steps

1 Design the integration flow

Configure the Endpoint URL and

2 Authentication.

Explore the communication

3 channel.

4 MID Server Usage.

5 User Profile.

Define Parameters, attributes or

6 fields.

7 Scripting.

8 Response.
Description Effort in hours

One way or two communication, which performs create and update.

2

The Endpoint URL depends on REST or SOAP method of Integration to

decide the flow. Authentication will be included within REST Message or in
HTTP Method.

HTTP Methods allowed operations are POST , PUT , GET and DELETE. 4
This process demands Outbound/ Inbound calls between the two
instances. Also we need we need to finalize between two webservice
methods REST or SOAP. 8

Involving MID will guarantee a secure connection for live environments. 8

Must have a webservice user with following roles (‘web_service_admin’

and ‘’rest_service’) assigned to it, if we are going to use a rest based
integration. Make sure the access to the application/table, which has ACLs
that allows for create and write operations. As ACLs take more
precedence than integration role, we must provide necessary roles for
accessing the table. 2

We need to maintain a Correlation ID in both the instance, maintain the

unique key. Also, if we were to update any record we use this Correlation
ID from one instance and search in another instance, if found then that
particular record will be updated.

In the form fields - notify Correlation ID field, populating this field is done
dynamically from a Business Rule available in Servicenow.
4
We need to use Business rule and Script include available in SNOW to pass
the values between two instances using the correlation ID. 16
For REST the format would be JSON (JavaScript Object Notation) and for
SOAP it is XML(Extensible Markup Language). 2