Transactions

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

• Data File: XML, CSV, EDI, JSON, Excel, PDF, Flat File

• API Data Source: Data or Metadata can be pulled directly from a live Justransform API connection like Salesforce, Shopify, or any cloud application.