Service definition concepts
Service definitions provide reusable execution logic for order management processing. They help reduce duplicate configurations and improve consistency across workflows by centralizing data processing, transformations, validations, and integrations.
Service definitions are composed visually on a canvas and reused across multiple actions, workflows, and transactions. They define the logic that runs during processing, while other configuration elements determine when and where that logic is invoked.
Example: Service definition usage
For example, when an order is created, a workflow can invoke an action that references a service definition. The service definition might validate order data, transform the payload, invoke an external system, and send a confirmation message. The workflow determines when the service definition runs, while the service definition defines the processing logic.
Service definitions
A service definition represents a unit of executable logic that actions can reference and invoke during order processing. Each service definition describes a flow of execution, including data handling, transformations, integrations, and application extensions.
Service definitions can support synchronous and asynchronous processing patterns, depending on how they are configured and invoked. They are commonly used to integrate with external systems, process messages, validate data, and transform information during order processing.
Service definitions are edited on the canvas and saved as named, reusable configurations. They do not control when execution occurs. They define what logic runs when started by other configuration elements.
Subservices
Subservices are the building blocks used to define execution logic within a service definition. They are added to the canvas and connected to describe how data flows and how processing steps occur.
Subservices include transport types, components, and adapters. Each subservice performs a specific function, such as starting an external system, transforming data, or running internal logic. Subservices cannot be run on their own and have meaning only as part of a service definition.
Service groups
Service groups organize service definitions in the service definitions list. They provide a way to group related definitions for discovery, reuse, and maintenance.
Service groups do not affect execution behavior. They control how service definitions are categorized and displayed in the user interface. Assigning service definitions to meaningful service groups helps reduce clutter and makes related logic easier to find and manage.
How service definitions are used
Service definitions provide reusable processing capabilities that actions invoke during order processing workflows to support the following capabilities.
- Execution of business logic during processing
- Integration with external systems
- Transformation and validation of data
- Event handling and messaging
Because service definitions are reused across multiple areas, changes to a service definition can affect several workflows and execution paths. Reviewing usage and impact before you modify shared logic helps maintain predictable behavior.
The relationship to other configuration areas
Service definitions define execution logic but do not control timing or flow. Other configuration elements determine when and where service definitions run.
- Actions reference service definitions and make logic reusable in process models
- Workflows and pipelines control execution flow
- Transactions define execution boundaries and triggers
This separation keeps execution logic independent from workflow design and invocation behavior, which reduces risk when logic changes.