A Transaction is an instance of a Message occurence. It contains and tracks the processing of a Message using Stages and HTTP Requests.
A Transaction is a vehicle used in the flow of Messages on a bonded ticket. It is essentially a container for a Request/Receipt pair. The Transaction record contains the necessary fields to facilitate and track both the movement and the processing of the pair of Messages.
A Transaction’s primary functions are:
- To contain the Request/Receipt pair of Messages.
- Handling the queueing of Requests and Receipts.
- Tracking the state of the Transaction from two perspectives:
- Transaction state
- The condition of the Transaction from a movement (transactional) perspective (i.e. the condition of the transport of the data).
- Process state
- The condition of the Transaction from a process perspective (i.e. its relation to the business logic that’s in place).
- System A sends a Request to system B to update the value of the
urgencyfield on a ticket without having ‘ownership’ of that ticket. The Request is properly formed and authenticated and is received in system B.System B sends a response acknowledging the Request and then subsequently processes the Request asynchronously. If, on processing the Request from system A, system B discovers that system A did not have the authority to change the value of the
urgencyfield, they would send a Receipt Message stating the error. That Receipt is also properly formed and authenticated and is received in system A without any problems.The Transaction state in this case would be set to ‘Complete’ as both the Request and the Receipt were transported successfully. However, the Process state would be set to ‘Rejected’ as system A did not have the authority to update the value of the
One of the many defining features of Unifi is its ability to track the state of the Transaction from both a transport (What’s happening with the movement of the message?) and a process (How does the content of the message align with business logic?) perspective.
Having the combination of these two states is extremely useful and gives a far more precise understanding of the condition of the Transaction and opens up more options. This means, for example, that an analyst can see and has the opportunity to fix issues based on a process error without the need for technical support (Unifi won’t break an Integration for a process error). For transactional errors Unifi can throw events which can be correlated to send notifications, or trigger the system’s Incident process as appropriate.
An outbound Message is being sent to the integrated system.
An inbound Message has been received from the integrated system (but not processed).
An outbound Message has been sent to the integrated system and we are awaiting an asynchronous Receipt.
We are sending an asynchronous receipt in response to receiving and processing an inbound Message from the integrated system.
An inbound asynchronous Receipt has been received from the integrated system.
The Message exchange was completed.
The Message exchange has been temporarily delayed because of incomplete transactions.
An outbound Message has been sent to the integrated system, but we have not received the asynchronous Receipt in the expected timeframe.
There was a transactional error with the Message exchange (e.g. invalid message format, unknown endpoint, code error etc.).
Transactions can be ignored manually to allow the integration to proceed.
This is configured on the integration by the value in the 'Async timeout' field.
This can be used when a Transaction does not complete (i.e. when it is in an ‘Error’ or ‘Timed Out’ state), or at any time when a Transaction is in progress or ‘Queued’ (e.g. when a system error occurs outside our control).
The Message is being processed and is awaiting a decision as to whether it falls within or outside of the scope of the business logic.
The Message has been processed and accepted as within the scope of the business logic.
The Message has been processed and rejected as outside the scope of the business logic.
The following table gives a description of the fields that are visible on the Transaction record:
The unique internal message identifier.
External message ID*
The external system’s unique message identifier.
The target table this record applies to.
The integrated ServiceNow ticket.
The integration this record belongs to.
The bond this record belongs to.
The message used to process this record.
The direction this record is travelling in.
The state of communication for this transaction.
The business logic process state.
Glide date time
The date and time the transaction was created.
Receipt due by
Glide date time
The date a receipt must be received before this transaction times out. Only applies to asynchronous transactions.
The internal communication error.
The business logic error in processing this transaction.
These are used in Unifi to match the related Requests and Receipts (i.e. the Message ID of one system will be used as the External message ID of the other system and vice versa).
The direction of the initiating (or first) Message in the Request/Receipt pair will determine the direction of the Transaction.
The value in this field can be rolled up to the bonded ticket, giving the analyst insight and the opportunity to resolve process errors.
You can view the transaction logs from the Transaction record by navigating to the 'Unifi Activity Logs' related list, or from the Unifi Operations Manager portal. This hugely significant feature offers considerably more detail than is available with the OOTB ServiceNow system logs and puts that information right where you need it - saving an inordinate amount of time hunting through the
Activity Logs will be populated if logging is enabled when debugging. They are particularly helpful to ShareLogic when debugging Unifi itself.
Unifi Operations Manager
Navigate to the 'Unifi Activity Logs' related list:
Clicking the 'View Logs' icon will open a list view of the logs in a new window.
Once the initial Transaction has completed, Unifi checks if there are any other transactions queued and processes them.
Here Unifi is processing the outbound HTTP Request and sending it to the integrated system.
Unifi is picking up the generated Stage data and generating an outbound HTTP Request.
A payload has been received from the external system and Unifi is processing that data and updating the target record within ServiceNow.
An inbound request has been received and generated an inbound HTTP Request.
The logs that can be viewed from the Transaction are for the Transaction itself and the Requests that relate to that Transaction.
Each of the logs relate to a specific part of the process flow, so depending on the direction of the Transaction the logs will occur in a different sequence. From a process perspective, the logs would occur as follows:
- Inbound request: RestHelper (relates to the inbound HTTP Request), Transaction receive message (relates to the inbound Transaction).
- Corresponding outbound receipt: Transaction sending (relates to the outbound Transaction Receipt), Request sending (relates to the outbound Request).
- When Transaction completes: Transaction process next queued.
- Outbound: Unifi Business Rule (relates to the logs defined in the Trigger on the process table being integrated), Transaction sending (relates to the outbound Transaction), Request sending(relates to the outbound Request).
For a synchronous integration that would be it. For an asynchronous integration Unifi would also expect the following:
- Corresponding inbound receipt: RestHelper (relates to the inbound Transaction Receipt), Transaction receive message (relates to the Receipt processing).
You can click the Replay button on the Transaction record to replay that transaction.
This will be used when testing/debugging. For example, if there is a transactional error, after you have investigated the cause & made any required changes you will want to replay the Transaction to check if the error clears.