Actions in process models

Actions define when processing logic runs within an order processing workflow. By associating actions with process steps, transactions, or events, you control how and when the system starts business logic as orders progress through pipelines. Actions help keep workflows predictable and adaptable by separating when logic runs from what logic runs, making process models easier to maintain and extend.

Overview

Actions are a core part of process modeling in Sterling™™ Order Management System. An action represents a trigger point within a process model that causes the system to start executable logic. Actions do not contain business logic themselves. Instead, they reference service definitions, which implement the logic that performs work such as data transformation, messaging, or integration.

By using actions, you add behavior to process flows without embedding logic directly in pipelines. This separation helps keep workflows readable while they enable reuse of services across multiple processes.

Actions apply reusable processing logic at specific points in order processing workflows.

What actions are

An action is a configurable element that applies reusable processing logic at a specific point in an order processing workflow. Actions reference service definitions and associate them with defined steps, events, or transactions within a process model.

An action has the following characteristics.

  • It references a service definition.
  • It is associated with a specific point in a process model.
  • It is triggered as part of normal process flow.

Actions define the timing of processing, not the implementation of logic.

When actions run in a process model

Actions can run at different points during processing, depending on how they are configured. Common trigger points define when actions run during a process model, such as these examples.

  • When a pipeline step is run
  • When a transaction starts or completes
  • When a specific event occurs in the order lifecycle

Because actions are tied to the process flow, they run automatically as part of pipeline execution when their trigger conditions are met.

How actions fit into process models

In process models, pipelines define the flow of execution, and conditions control branching. Actions are placed at specific points within that flow to start logic at the right time.

A typical sequence shows how actions execute within a process model.

  1. The pipeline reaches a configured step.
  2. Conditions determine the next path.
  3. An action that is associated with the step or event is triggered.
  4. The referenced service definition runs.
  5. Processing continues based on the outcome.

This layered approach separates flow control, decision logic, and execution, which makes models easier to understand and modify.

Relationship to service definitions

Actions and service definitions work together:

  • Actions define when logic runs.
  • Service definitions define what logic runs.

Multiple actions can reference the same service definition, which enables consistent behavior across different workflows without duplication. Changes to a service definition take effect wherever actions reference that service.