Defining Transactions
  • 03 Oct 2022
  • 2 Minutes to read
  • Contributors
  • Dark
  • PDF

Defining Transactions

  • Dark
  • PDF

Business scenario

Consider a scenario where a user has an e-commerce application and one of the modules in the user's application is to process the orders which may involve several transactions such as managing the orders, fulfilling the orders, shipping the orders, etc.

Order processing can be considered a business process in Serverless360 Business Activity Monitoring (BAM), and the list of transactions involved in this business process can be considered business transactions, which are New Order, Fulfill Order, and Ship Order.

Consider the transaction Fulfill Order for this demonstration, which will involve receiving the orders, and segregating the orders based on their validity.

If it is a valid order, the order should be accepted. Otherwise, the order should be declined. Thus, the activities involved in this transaction are getOrders, segregate orders, accept orders, and decline orders.

The steps that can be taken next are as follows:

  • Now, the user has to create a business process, order processing.

  • Users can create a list of stages for the business transaction.

  • Users can also configure the stage properties.

  • Click here to know more about how to create a business process, to define milestones(stages) in a transaction.

  • Click here to know about how to create stages such as get orders, segregate Orders, acceptOrders, drop orders with the properties that users need to track for every stage.

  • Click here to know more about how to configure properties.

Add a Transaction

  • To add a business transaction for a business process, press the Add button in the Transactions pane available in the Transactions section of a business process.

  • Tracking name is a name given to a business transaction that is used to identify the transaction while tracking data. Friendly name is a name assigned to it that appears only in the Business Activity Monitoring user interface for tracking data.

  • Select one among the available options in the Direction dropdown to represent if the transaction is Inbound or Outbound.

  • Choose one or more of the appropriate status during which a transaction instance can be reprocessed. A transaction instance cannot be reprocessed if its status does not match any of the selected statuses.

  • Enter the time period to purge the older data in the Purge data older than field. Click the Create button complete adding a transaction to the corresponding business process.


Update a Transaction

  • Business transactions of a Business process can be updated at any time to meet the business needs of users. The details including the default reprocess stage, the stage status for reprocessing, the purging time period and the basic details can be updated.


Import/Export a Transaction

  • Users can import and export a business transaction with the help of respective buttons available in the Transactions pane.

Export and import Business Transaction.gif

Clone a Transaction

  • Business Activity Monitoring provides users an option to clone their business transactions with the help of a duplicate icon present within the transaction in the Transactions pane.

  • The user must provide a tracking name as well as a friendly name for the transaction to be cloned.

  • The cloned transaction will have the same internal configuration as the original transaction. Only the tracking and friendly names will be unique.

  • The changes made in the original transaction will not get reflected in the cloned transaction.

Clone Transaction.gif

Added information

  • The users can aggregate transactions and stages in any way they want, and there are no restrictions on how they can do so.

  • In Business Activity Monitoring, the transaction will be implemented as an activity diagram which will be a familiar view to operators and business users.

Was this article helpful?