Lifecycle statuses and tracking

Lifecycle statuses define the states that a document moves through in a pipeline. Transitions and rules determine how the document progresses between those states. Together, these elements control how progress is tracked and how lifecycle behavior is enforced.

Status definitions

A status represents a specific point in a document lifecycle, such as created, scheduled, released, or completed. These states provide a consistent way to track progress and communicate meaningful lifecycle points to users, integrations, and downstream logic.

A transaction can include two types of statuses.

Drop statuses indicate that a transaction has completed.
Pickup statuses move the document from one transaction to the next.

The system provides base statuses for common lifecycle stages. These statuses connect transactions and define standard lifecycle flow. You can extend these statuses to represent business-specific milestones without modifying product configurations. Extended statuses do not exist independently. They follow the base status from which they are extended and preserve upgrade safety.

Statuses are defined independently from workflows so they can be reused across process models and applied consistently wherever lifecycle tracking is required.

Status transitions and rule evaluation

Status transitions define the valid paths that a document can take as it moves through its lifecycle. They describe how one state leads to another and prevent invalid progression.

Rule evaluation determines when a status applies. The system evaluates conditions, execution outcomes, and system events to decide whether a transition occurs. This approach helps ensure that lifecycle progression aligns with business logic and processing results.

By combining transitions with rule evaluation, process models can support multiple execution paths and maintain control over document progression.

Monitoring rules and lifecycle evaluation

Monitoring rules define how the system evaluates and tracks lifecycle behavior for a status. They combine conditions and actions to determine when a status is reached and how the system responds.

Monitoring rules perform the following functions:

Evaluate the conditions that define when a status applies.
Run actions based on evaluation results.
Track lifecycle progress over time.

This approach makes lifecycle behavior observable and configurable within the context of each status.

Milestones and lifecycle tracking

Milestones represent key checkpoints for a status. They provide a way to measure progress, monitor timing, and show important lifecycle events.

Milestones are associated with statuses and are used to support lifecycle tracking in the following ways:

Track when a document reaches significant lifecycle points.
Measure performance against expected timelines.
Provide visibility into lifecycle progression.

Monitoring rules determine when a status applies. Milestones record when that status is reached and track lifecycle progress.

Relationship to process flow

Statuses define what lifecycle states exist, while conditions, rules, and services define how and why documents move between those states.

Conditions evaluate logic that influences status evaluation.
Monitoring rules determine when statuses apply and track lifecycle progression over time.
Transitions define valid movement between statuses.
Actions and services run when status changes occur.
Milestones track lifecycle checkpoints.

Together, these elements define how documents move through workflows, how decisions are applied, and how lifecycle progression is observed and measured.