July 2020 – Enable Professional Services

eBonding Integration Between ServiceNow Instance

July 16, 2020July 27, 2020
by Nicole Bailey

What is eBonding?

With respect to ServiceNow, eBonding means the creation of bi-directional integration across ServiceNow applications.

Benefits:

The main benefit of an eBonded solutions is that they typically provide a “synchronised” exchange. This means that data is shared automatically and two applications will always have matching data. This can reduce the amount of manual intervention normally required to sync the systems.

Key Feature:

Automation and simplification are the keys to improving efficiency and saving both time and money. eBonding helps in this by simplifying an array of tasks and keep the required system in sync to deliver requests efficiently.

Capability:

ServiceNow out of the box (OOB) capability provides setting up of two eBonded systems using Integration Hub. It uses common integration patterns to synchronise incidents across different ServiceNow instances.

Availability out of the box OOB:

ServiceNow eBonding spokes provide out of the box actions which helps in the synchronisation:

Create Remote Incident action
Lookup Remote Incident action
Update Remote Incident action

Pre-Requisites

In order to have eBonding in place, a HTTP connection record should be created by providing the credential for authentication and details of the URL to be connected.

Subscription:

**The ServiceNow eBonding spoke is included by default in your instance and doesn’t require an Integration Hub or Orchestration subscription.

Written by:

Avinash Kumar Sharma

Senior Technical Consultant

Learn more about Avinash – follow on LinkedIn – https://www.linkedin.com/in/avinash-kumar-sharma-378a9466/

Uncategorized

Creating custom Scoped App via Studio

July 1, 2020October 8, 2020
by Nicole Bailey

Scoped App Vs Global App

Scoped applications are sandboxed into their own application, thereby heavily restricting their ability to cause any performance issues to other running applications.

In the past with a global application, you could write some bad code which could also impact other processes because you can reference the, for example, the incident table and cause major issues to other processes. With scoped applications, they are much more restricted and are therefore considered safer to install on an existing instance with virtually no chance of any side effects to other existing applications.

They are also more secure in terms of who can access them, for instance, the new Scoped HR Application is locked down in order for HR only users to be able to access HR Data, not even admin can access the scoped application.

Steps to create a custom app

1. Go to STUDIO >> Create Application