Process is the top level configuration element which contains all Integrations for the Process concerned (e.g. Incident, Problem, Change, Request etc.).

Process is at the top of the configuration chain in Unifi. It is a mechanism which provides functionality not provided OOTB in ServiceNow. The purpose of a process is to keep like integrations in one place (e.g. Incident process integrations, or Change process integrations).

One Process may contain multiple Integrations which can each be configured separately and uniquely (more on that on the Integrations page).


The fields to be configured in the Process record are as follows:






The name of the ServiceNow process being integrated.

API Name*


The unique name of this process for use with the API.

Target table

Table name

The primary target or process table that this integration uses.

Reference field

Table name

The field on the target table that is used as the reference for the external system.

Stage table**

Table name

The table for storing staged data.



Application containing this record.

SOAP Service***


The Scripted SOAP Service that external systems will connect to.

REST Service***


The Scripted REST API that external systems will connect to.



A description of what this Process is for and/or how it works.

*API Name

The API Name is how we identify which Process we are integrating with. The Scripted SOAP/REST Service will reference the API Name (which is why it is important for this to be a unique reference).

**Stage table

All Integrations for this Process will leverage the one Stage table.

***SOAP/REST Service

When building an Integration & after configuring the relevant SOAP/REST Service, populate either of these fields with the relevant value to enable Unifi to include that Service in the packaged Integration. See the 'Web Service' page (of the Bidirectional Asynchronous Incident Guide) for an example.