onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
PackagePackagetypeA library you install and call yourself.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

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.

Adds status-transition flows to a CAP Java service, part of the cds-services-bom release line. In CAP Node.js support for flows is built in and available out of the box; for CAP Java it is this feature, added with runtime scope in srv/pom.xml, that provides it. A flow is modelled with three annotations on a bound action: @flow.status marks the entity's status element, and @from and @to declare the entry and target states of a transition; a generic handler then rejects an action whose entity is not in one of the states named in @from with a 409 Conflict, and moves the status to the state named in @to once the action runs. SAP Fiori elements UIs pick this up automatically and enable, disable or refresh the transition buttons accordingly.

Homepage
Docs

Facts

LicenceSAP DEVELOPER LICENSE AGREEMENT for CAP

Where it sits

Lives in
CAP
Provides
Status flowsCAPStatus flowscapabilityDeclaring 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 validation](capability:input-validation): that checks a value, this checks a transition. Not [workflow integration](capability:workflow-integration): that drives an external engine, and this stays inside the model.
Flavors
Java

What it declares

Every artifact

Type
Package
Origin
By SAP
Runtime
Java

As a package

Where it runs
does not say
Distributed through
does not say

Connections1

Others providing1

Compare all 2 on the Status flows page →
Status flows
  1. @sap/cdsCAP Node.js runtimefrom CAP

Details

Sources1
Added by handdiscovered herechecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesjava
discovered viaAdded by hand
first seen in the atlas
ecosystem and domaincap, process-and-workflow
Flavors1
Java
“For CAP Java, it is provided by the feature” — Status-Transition Flowschecked
History in the atlas2
  1. Adds the CAP Java implementation of status-transition flows: a generic handler validates the entity's current state against a bound action's entry states before the action runs, and updates the status to the target state afterwards.
  2. First seen.
For your agent
Ref
artifact:cap-java-cds-feature-flow
JSON
/artifacts/cap-java-cds-feature-flow.json
MCP
Connecting an agent