Search…
Message Identification
Unifi needs to identify the name of the inbound message in order to know how to process the inbound data.
When we configured our Outbound Incident Integration we weren't concerned with identifying inbound messages, because there weren't any (we were only sending outbound).
Now that we're polling our PDI for data as well as sending data, we need to be aware of the above concern.
To facilitate this we need to make a change to our Integration.

Message Identification

This script is necessary because we have chosen to include the Message name in the structure of the payload object (see Response Script on the 'Poll Processor' page). If we had chosen instead to set it in the options object, it would have been processed and passed to Unifi for automatic Message identification - without the need to configure this script.
To enable the Integration to identify which messages to use to process inbound requests:
Navigate to the 'Integration' icon to open < Your Integration >, then navigate to Integration > Message Identification.
1) Update the code in the 'Identify message script' field so that it looks like this:
1
function identify(payload) {
2
3
return (payload.message.name || '') + '';
4
5
}
Copied!
The Message Identification form should look like this:
2) Save.
In order for both systems to identify and understand which records are bonded, we need to make a few more changes which we shall group together under the heading of Bond Identification.
Last modified 2mo ago
Export as PDF
Copy link