Process & Workflow
Work that spans people and systems over time: business processes that are automated, and the workflow steps a person completes inside them.
Capabilities
Declaring allowed status transitions in the model
Driving an external workflow engine and reacting to what it emits
Recent changes
Workflow integration core coverage reassessed
Workflow integration core coverage reassessed
Workflow integration A second engine, n8n, gained the same first-party treatment the core had already given SAP Build Process Automation. Before it, triggering an n8n workflow from CAP meant the independent sleibach/cap-n8ncap-n8nMaps CAP onto n8n: a programmatic workflow API, @n8n.trigger annotations dispatched through the transactional outbox, and a typed cds import --from n8n.independent, cap plugin or a hand-wired HTTP call; after it,
@n8n.process.starton an action or event, or the programmaticn8nservice, triggers a workflow with credentials resolved through config, a Cloud Foundry binding or a BTP destination.Workflow integration The core gained a first-party way to drive SAP Build Process Automation from a CAP service. Before it, starting or managing a process meant hand-rolling calls against the workflow API through a destination; after it, a built-in generic ProcessService covers start, suspend, resume and cancel without any import, and importing a specific process additionally generates a typed CDS service with ProcessInputs, ProcessOutputs and ProcessInstance types.