A Single Transaction Event

As explained in the prior topic, a business process consists of multiple data points known as audit events. As an example, an order-to-delivery business process could contain: an Order Receipt event, an Order Validation event, a Delivery Order event and an Order Shipment event. Each event can be logged and recorded. A chronological progression of these audits events is a business process.

A transaction is a single end-to-end activity of the business process. Each transaction is usually assigned a numeric or alphanumeric value. As a consumer this may be the Invoice number or Order number that you see when you make a purchase. Within TIBCO Cloud™ AuditSafe, this assigned value is called a transaction_ID. This information is set-up during configuration and allows you to track a single transaction from beginning to end.

In addition each audit event within a transaction contains information that is also configured during set-up:

• Each event uses a customer-assigned event_id. This identifies each event within a transaction. If an event_id is not configured during set-up, the system uses a time stamp to chronologically chain events containing the same transaction ID.
• Each event also contains different statuses (or stages). For example, when an order is placed it’s status = “New” when the customers credit is validated it may move to a status of “In Progress”, and so on.

The transaction_ID is the glue that binds all of these events and event statuses together.

For information about events and event status, continue to Audit Events and Event Status .