Order processing workflows

Overview

Order processing workflows describe the control flow of order management. They define the steps an order follows, the points where decisions are evaluated, and the paths that processing can take as conditions change. Workflows provide the structure within which transactions, actions, and services run.

Rather than embedding logic directly into execution, workflows separate flow definition from decision logic and execution behavior. This separation helps keep processing models clear and adaptable as requirements evolve.

Base process types

Base process types define high‑level processing patterns for orders and related documents. They represent major phases of order handling, such as order creation, fulfillment, or cancellation, and establish the context in which workflows execute.

Base process types do not define individual steps. Instead, they provide a reusable foundation that pipelines build on to define detailed processing behavior.

Process type pipelines

Process type pipelines define the ordered sequence of steps that implement a base process type. Pipelines break processing into discrete steps that can evaluate conditions, trigger actions, update statuses, or invoke transactions.

Each pipeline represents a specific processing path and serves as the primary structure that governs how orders are handled at runtime.

Pipeline steps and flow sequencing

Pipeline steps represent individual points within a workflow where processing occurs or decisions are made. Flow sequencing defines the order in which these steps run and how control moves from one step to the next.

Sequencing determines:

• When conditions are evaluated.
• When actions or transactions are triggered.
• How processing progresses or branches.

Clear step sequencing helps ensure predictable and repeatable order processing.

Pipeline determinations

Pipeline determinations control which pipeline is selected at runtime. They evaluate document data and configuration context to choose the appropriate processing path for an order.

By using pipeline determinations, you can apply different workflows dynamically without duplicating process definitions. This approach supports variation in processing behavior while preserving a consistent workflow structure.

How workflows fit into order management behavior

Order processing workflows sit at the center of order management configuration. They:

• Provide the structure that conditions use for branching.
• Define where transactions and actions are triggered.
• Drive status changes and lifecycle progression.

Other configuration elements operate within workflows, but workflows define the overall path an order follows through the system.