Status flows
Declaring in the model which status transitions an entity may make, so the runtime rejects a transition nobody declared and sets the status itself when the bound action runs, instead of a check written by hand in every handler. Not input validationInput validationRejecting bad input before it reaches the database. While this can be done manually inside a handler, there are solutions in place to derive type, range, enum and mandatory checks from the model definitions.SAP and community, unassessed: that checks a value, this checks a transition. Not workflow integrationWorkflow integrationDriving an external workflow or automation engine from an application and reacting to what it emits — triggering runs transactionally and importing the engine’s shape as a typed model.SAP and community, core adopted it: that drives an external engine, and this stays inside the model.
Overview
@sap/cds Validates and executes the status transitions modelled with @flow.status, @from and @to on bound actions in the generic handlers, out of the box; in CAP Java the same is the cds-feature-flow package.
com.sap.cds:cds-feature-flow Adds declarative status-transition flows to CAP Java: entry and target states on a bound action, validated and applied by a generic handler that answers 409 Conflict from a wrong state.
Not covered: Only bound actions can be flow-controlled: plain CRUD and draft operations cannot be restricted by a flow. On a draft-enabled entity every action is disabled while a draft is open, so a transition can only be performed on the active instance.
No community artifact is documented here.
Artifacts
Content
Details
Coverage
For your agent
- Ref
capability:status-flows- JSON
- /capabilities/status-flows.json
- MCP
- Connecting an agent