Defining transactions for process steps

Defining transactions for process steps specifies when processing runs and how work is grouped within order processing workflows. By associating transactions with process steps, you control execution timing, sequencing, and how changes are finalized or reversed.

This approach helps ensure predictable execution, protects data consistency, and supports controlled handling of success, failure, and retry scenarios during order processing.

Overview

Transactions define execution boundaries within order processing. When you associate a transaction with a process step, you determine how related work is grouped and when execution occurs as orders move through workflows. Transactions also govern how the system commits or rolls back changes based on processing outcomes.

You can extend or derive transactions to support specialized processing scenarios without redefining core behavior. As workflows evolve, transactions can be modified or removed to align execution timing and dependencies with updated requirements.

Create, modify, and delete transactions used in process steps, including extending or deriving transactions from existing definitions. These tasks build on the execution concepts that are described in Execution boundary and timing configuration and show how transaction behavior is applied in practice.