Defining lifecycle statuses

Define and manage lifecycle statuses to represent the states that a document moves through. Control how documents move between those states and define how lifecycle behavior is evaluated and tracked. These configurations help ensure that workflows follow valid paths, reflect business milestones, and provide clear visibility into order processing.

The system provides a predefined set of statuses that form the base lifecycle, such as Created and Scheduled. These statuses connect transactions and represent key lifecycle points. The system advances a document to a new status when the events and conditions of a transaction complete. Statuses are defined independently from workflows so that they can be reused across process models.

Status transitions use drop and pickup statuses to move documents between transactions. A drop status marks the completion of a transaction. A pickup status starts the next transaction and moves the order to the next stage.

Extend lifecycle tracking by defining other statuses that align with your business processes. Extended statuses must follow an existing base status and cannot exist independently. Use these extensions to refine lifecycle visibility without changing the foundational workflow structure.

Use these procedures to safely extend lifecycle tracking and refine how statuses are applied. Define how the system evaluates lifecycle behavior and tracks lifecycle progression.