Date: Thu, 28 Mar 2024 11:34:07 +0000 (UTC) Message-ID: <572593717.243.1711625647275@ip-10-0-0-180.us-west-2.compute.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_242_1146549841.1711625647270" ------=_Part_242_1146549841.1711625647270 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Perspectium uses a wide range of terms and concepts that you may not be = familiar with. We've put together this basic overview page that introduces = some of the main terminology you'll likely encounter as you navigate throug= h the application and this docs site.
Below, you'll find a general definition of the term, some context as to = when/why it might be used, and links to where you can find more information= , including setup and customization instructions.
The Integration Mesh is Perspectium's flagship cloud service that acts a= s an intermediary between two software platforms, allowing for seamless dat= a integration. The Integration Mesh is used with both DataSync a= nd ServiceBond products.
A dynamic shar= e is a feature that allows for real-time sh= aring of ServiceNow records as they are created, updated, and/or deleted. I= n other words, dynamic shares are caused by some triggering event (such as = when incidents are created, updated, or deleted). The data is shared t= o a subscriber, which can be another instance of ServiceNow, the DataSync A= gent, or any number of the other applications that Perspectium can integrat= e with.
When might you want to use dynamic share?
The main purpose of dynamic share is to set up triggering events, so rec= ords are shared out dynamically according to specific trigger conditions=E2= =80=94when records are created, updated, or deleted. So, your organization = would benefit from dynamic share if you want to be consistently notified if= and when any of these events occurs.
For example, you can set up a dynamic share so that any time a new custo= mer service ticket is created in ServiceNow, it automatically triggers a ti= cket to also be created in a subscribing application, such as Salesforce, J= IRA, or another ServiceNow instance.
A bulk share is a&n= bsp;feature that allows a ServiceNow instance to share a pre-filtered range= of data all at once. The data is shared to a subscriber, which can be anot= her instance of ServiceNow, the DataSync Agent, or any number of the other = applications that Perspectium can integrate with.
This feature can share multiple tables through the table hierarchy,= run through advanced filters and scripts, share out related/auxiliary reco= rds, and more.
When might you want to use bulk share?
Since this feature allows you to share a big dataset all at once (hence = "bulk"), it removes the need for manually sharing out data individually (al= though that is still an option). If your organization wants to send a datas= et from ServiceNow to another application (whether that is another ServiceN= ow instance or some other application), setting up a bulk share allows this= to happen with ease.
Bulk shares can even be scheduled to run at specific time intervals, lik= e daily, weekly, monthly, or on any other sort of custom schedule. Or even = just once at a specific time. You can schedule these however you want. = ;
As mentioned above, scheduled bulk shares are simply bulk shares that ar= e scheduled to run at specific time intervals, or at one scheduled time.&nb= sp;
Queues are how outbound and inbound messages are stored in sp= ecific order when you are sharing data out from ServiceNow (or another appl= ication, such as Salesforce) into a subscribing instance. When you share ou= t data using a dynamic or bulk share, the relevant (outbound) messages get = stored in a shared queue before they are processed by= the Perspectium Intergration Mesh, and are then pass= ed into a subscribed queue, where they (now inbound m= essages) are stored before being passed onto the subscribing instance.
Shared queues are set up in the sharing instance, and subscribed queues = are set up in the subscribing instance.
The use case for shared queues is universal, since you need to set up a = shared queue in order to share out data.
A Mu= ltiOutput job is a scheduled job that processes the outb= ound messages that are ready to be sent from a shared queue to the Integrat= ion Mesh.
Essentially,=
this job works by going to your outbound messages table and sending out th=
e messages per queue, and this is typically done by a single job.
A ServiceNow table map is used to map ServiceNow field data for records being shared = out. Then, a ServiceNow = transform map is used to determine the relationships between field= s in a table map being shared with fields in a subscribing ServiceNow table.
If the field names of the record being shared out from ServiceNow need to = be modified, or if the value of one or more fields needs to be transformed,= you can create an outbound table map to modify the fields for your integra= tion.
Common documents<= span> are XML schemas that represent the fields that can be map= ped from one application to another.
Bonding a Perspectium-supported a= pplication with ServiceNow requires the use of Common Documents.