Home / Product / State tracking

Guide work through a lifecycle

Make the next valid step clear—and preserve how the work got there.

Define allowed stages for each record and store every accepted transition beside its subject and actor.

01Permit only the state transitions declared for the record lifecycle.Only accept movements declared for the current state.
02Create a shared languageGive product and operations the same names for progress.
03Keep transition evidenceConnect the state history to the record it describes.
Why it matters

A status field can say where work is. It rarely says what is allowed next.

Require requests to move from draft through the configured review stage before completion. Permit fulfillment only from the approved order states. When state is just free-form text, every screen and automation must remember the same transition rules.

Daptin lets a resource use a declared state model with an initial state and named events that move it between allowed stages. A transition updates the record's state context and leaves history.

Actions and permissions can then build on that lifecycle: the right people see the right next operation, reports can summarize where work is, and investigations can follow the path.

01

Make progress understandable

Use meaningful stages that product and operations can discuss.

02

Validate every requested state change against the declared transition map.

Validate the requested event against the record's current state.

03

Turn history into context

Show the current state and every accepted transition that produced it.

Keep each item understandable over time

Add customer language, change history, and clear progress stages.

The same article, case, product, or order can appear in the reader’s language, retain who changed what, and move only through allowed business decisions.

Diagram showing one business item connected to language editions, a dependable change history, and clear progress stages.
Give every business item useful contextPresent the right language, preserve earlier information with the responsible person, and make the current and next stages explicit.Open diagram for full-size view
How it fits

Part of one connected backend.

State tracking does more when it can reuse the records, people, access rules, and workflows already in your application.

Step 1Declare

Name the stages and allowed events between them.

Step 2Start

Create the record in its initial state.

Step 3Transition

A permitted request applies a valid event.

Step 4Remember

Store the new state and its transition evidence.

What it enables

Use it in products people recognize.

Start from the experience you want to create; the backend capability supports the work behind it.

Approval process

Move a submission through draft, review, approval, and rejection.

Service request

Track received, assigned, in progress, waiting, and resolved.

Content lifecycle

Guide an article from draft to review, scheduled, published, or archived.

Know the boundary

What Daptin leaves in your hands.

Use state tracking for finite transitions and compose broader processes with actions, events, and schedules. Complex branching, timers, compensation, parallel work, and human assignment may require actions or a specialized workflow system.

Understand the operating responsibility →

Build from one foundation

Declare valid record transitions once and store every accepted change beside its actor and subject.

Run Daptin locally, explore the live administration surface, and follow one complete application path.