Skip to main content

ServiceNow Integrations Interview Questions - Relevant & Important

ServiceNow Integrations Interview Questions

1.> What is ServiceNow Integrations ?

Integrations means establishing the connections between two Applications or Systems so they can interact with each other.

In simple language, Applications can communicate with  each other. Basically, we can send or receive the data from third party tool or another applications to ServiceNow.

ServiceNow Platform allows direct Integrations for software, infrastructure, Products and APIs. This will enable your enterprise to transfer the data from legacy systems into the Platform as well export the data from ServiceNow into applicable System.

2.> What is Uni-directional and Bi-directional Integrations?

A Unidirectional interface sends data in only one direction form a sender to a receiver & Unidirectional relationship has only an owing side.

A Bidirectional interface send involves in exchange of data or information between two systems & It has both an owing & inverse sides.

3.> What is Inbound Integrations in ServiceNow ?

Inbound web services are designed to provide third parties with the ability to retrieve (GET) or update (POST) data in ServiceNow.

Inbound means that other applications make calls to Service Now's REST API to get information from SN, or create/update records.

Request comes to ServiceNow from other System or third party tool & is being acknowledged & response will be sent to other tool from ServiceNow.

4.> What is outbound Integration in ServiceNow?

Outbound means that ServiceNow makes call to other applications' REST API to get information from the other application or create/update records.

 while outbound web services allow ServiceNow to initiate a transaction with a third party (also using either GET or POST, etc.) 

Incident is being created in Target system (third party tool or other application), request will be sent to target system from ServiceNow. It will be acknowledged there & response will be sent to ServiceNow.

5.> Difference b/w Rest & SOAP API?

REST stands for Representational State Transfer whereas SOAP stands for Simple Object Access Protocol. 

REST is an architectural pattern whereas SOAP is a protocol. REST work with plain text, XML, HTML and JSON whereas SOAP only works with XML format for communication & transfer of data. 

REST doesn’t need much bandwidth whereas SOAP needs more bandwidth for its usage. 

REST has SSL and HTTPS for security, On other hand SOAP has SSL( Secure Socket Layer) and WS-security due to which in the cases like Bank Account Password, Card Number, etc. SOAP is preferred over REST. It’s more secured. 

REST is easy to understand & fast rather than SOAP.

6.> What is Rest (Representational State Transfer) API in ServiceNow?

REST APIs were designed to take advantage of existing protocols. ServiceNow Tool provides a variety of methods to integrate with other applications such as Jira, Event monitoring tool, LDAP etc using REST. 

You can use REST interfaces to access data on your instance. Service Now's REST API Explorer is an application to construct and test API requests to a ServiceNow instance Inbound web services, such as the REST API, allow you to interact with ServiceNow instance data using web service requests. 

ServiceNow outbound REST functionality allows you to retrieve, create, update, or delete data on a web services server that supports the REST architecture.

7.> What is Table & Import Set API?

The Table API allows you to perform create, read, update, and delete (CRUD) operations on existing tables & retrieves multiple records for the specified table. 

The Import Set API allows you to interact with import set tables & API transforms incoming data based on associated transform maps. The import set API supports synchronous transforms.

8.> What are response & request Objects?

request-response is a message exchange pattern in which a requestor sends a request message to a target system. The target system receives and processes the request, and if all goes well, it returns a message in response.

requests sent by the client to trigger an action on the server, and responses, the answer from the server.

request is sent to target system to request something, in response to the request, acknowledgement is sent from target that is response.

9.>What are https methods?

Https means hypertext transfer protocol which is an application layer protocol for distributed, collaborative & hypermedia information system. 

It is foundation of data communication for the World wide. HTTP functions as a request–response protocol in the client–server computing model. 

HTTP specification specifies how clients' request data will be constructed and sent to the server, and how the servers respond to these requests.

10.> Types of https method ?

GET - It is used to retrieve or read the record from the given server 

POST – to create new record from the given API 

PUT – to update the partial or specific records, It will check if resource exists then it will update the record or else it will create that record 

PATCH – to update the whole record, It will always update a resource 

DELETE – to delete the record



Comments

Post a Comment

Popular posts from this blog

How to use getreference() with callback function in client Script | #ServiceNow

What is the use of getReference() ? getReference() gets the record used in another reference field. For example you have the requested_for (reference to the sys_user table) and with getReference, you will retrieve the User record and save this as a gliderecord into a variable. Why we use callback function with getReference?  callback function allow you to use asynchronous processing with your getReference call. Example: FetchCompany&phoneNo function onChange(control, oldValue, newValue, isLoading) {    if (isLoading || newValue == '') {       return;    }  var requester_user = g_form.getReference('requested_for', callback); function callback(requester_user) { g_form.setValue('email_id',requester_user.email); g_form.setValue('manager', requester_user.manager); } }

Difference b/w After & Async Business Rule in ServiceNow

Let's try to understand difference b/w  After & Async Business Rule & some examples on Real time scenario of After Business Rule & Async Business Rule : 1.> After BR executes synchronously (It will wait for a result, once result is ready & get displayed then user will get control to do anything, user has to wait) but Async BR executes asynchronously (user will get control immediately, it will not halt the user and result will get displayed when its ready or get response from system, it will be executing in the background as per system scheduler). 2.>After BR is used to update information on related objects that need to be displayed immediately such as GlideRecord queries etc. whereas Async BR is used to update the information on related objects that do not need to be displayed immediately such as calculating metrics & SLA etc. 3.>We can use current & previous objects but We can’t use previous object in Async rule & current object can’t be refere

Access Control List (ACL) in ServiceNow

First, Let's understand what is Access Control List (ACL) in ServiceNow? Access Control Lists are the process by which ServiceNow provides granular security for its data and can be applied to individual records, as well as fields within those records. Rules for access control lists (ACLs) restrict access to data by requiring users to pass a set of requirements before they can interact with it.  All access control list rules specify:  1.> The object and operation being secured  2.>The permissions required to access the object There are some important ACL record operation types  - create : Enables users to insert new records (rows) into a table. read : Enables users to display records from a table. write : Enables users to update records in a table. delete : Enables users to remove records from a table or drop a table. edit_task_relations : Enables users to extend the Task [task] table. edit_ci_relations : Enables users to extend the Configuration Item [cmdb_ci] table. save_as_