/
Transactions

Transactions

Owned by Rohitashva Gaurava
Last updated: May 13, 2020 by Keith Lawlis
3 min read

The JT Transaction Console provides a real time network dashboard and transaction and event pane for every transaction processed within a given tenant environment.

To Access the Transaction Console, click the Transaction button from the left pane

The user will be defaulted into a transaction view for recent transactions.

Users can also access older transactions (archive) transactions, by clicking on the Archive Transaction as shown below.

 

Metadata displayed as column headers are sortable. The definition for this metadata is described below.

  • Transaction ID: This contains a unique transaction ID for the processing event. A transaction ID may be original ID or may also contain the following to prefixes

    • “S” = Sub Transaction (eg. S 987654321) - Represents a Sub transaction and the ID represents the original transaction ID. In this example the transaction represents a replay from the original transaction 987654321. Sub transactions may get created from the Business Process configuration and may represent use cases such as unique transactions within a batch. The batch may represent the original transaction and the sub transaction the processing of the unique transaction within the batch.

    • “R” = Replay Transaction (eg. R 123456789) - Represents a Replay transaction and the ID represents the original transaction ID. In this example the transaction represents a replay from the original transaction 123456789

  • Replay Status: This data contains whether the transaction is the original or if it is a manually replayed transaction

    • Original Transaction

    • Replay Transaction - Represented with a “R” prefix.

  • Status: Represents State of Transaction: Transaction states include: Success, Warning, and Failure

    • Success - Transaction processed Successfully

    • Warning - Transaction occurred a “Warning” condition based on validation rule, but processing completed as configured

    • Failure - Transaction occurred a Hard Failure, and an alert if configured triggered for the event.

  • Start Time: Represents the Start Time of the transaction record represented in UTC time zone

  • Source Connection: Contains the name of the Source Connection used within the Business Process. This data represents the connection that originated the transaction. The data will be pulled from the name of the Connection configured via “Connections”

  • Destination Connection: Contains the name of the Destination Connection used within the Business Process. This data represents the connection that the output data will be sent to. The data will be pulled from the name of the Connection configured via “Connections”

  • Complete Time: Represents the Start Time of the transaction record represented in UTC time zone