onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
All CAPNode.jsJava
CapabilityUI & Frontend BridgeNode.js, read from its artifacts

Draft handling

Letting a user edit a record over several requests before it becomes real — draft activation, locking, and the semantics Fiori elements expects.

Showing artifacts, examples and content with confirmed Node.js applicability. View All CAP

Overview

SAP SHIPS
@sap/cds

Runs the draft lifecycle for draft-enabled entities — activation, discard and locking — without custom handlers. Since CAP Node.js 10.0 a request that carries no draft notation addresses active data, and draft locks are still enforced against direct updates, deletes and conflicting edits.

SourceServing Fiori UIs — draft supportchecked

A Node.js coverage assessment has not been written. View all flavors

THE COMMUNITY ADDS
@rizing/cds-extension

Runs the draft lifecycle over entities projected from an imported remote OData service, and generates a temporary value for a semantic key on draft creation.

Source@rizing/cds-extension — READMEchecked
cap-collaborative-draft

Turns a CAP Node.js draft from one editor's into several editors'. A user opening a draft that already exists joins it rather than being refused, the plugin deploys DRAFT.DraftParticipants, DRAFT.DraftFieldLocks and DRAFT.CollaborativeDraftState alongside the standard draft tables, and any participant can activate rather than only the originator. Fiori elements is told through injected $metadata: CollaborativeDraftEnabled, DraftAccessType, a DraftAdministrativeUser navigation property for the avatar group, and a ColDraftShare bound action behind the invite dialog. Entities that do not carry @CollaborativeDraft.enabled are untouched.

Sourcesleibach/cap-collaborative-draft — READMEchecked

A Node.js coverage assessment has not been written. View all flavors

Artifacts5

5 of 5 artifacts
ArtifactSignals
CDS plugins3
@rizing/cds-extensionCAP plugin putting a draft-capable facade in front of imported OData
Signals
none
cap-collaborative-draftCollaborative draft support for CAP Node.js services
Signals
Functional boundary
cap-handler-frameworkConvention-based handler layer for CAP with draft lifecycle hooks
Signals
none
Packages2
@sap/cdsCAP Node.js runtime
Signals
none
@sap/cds-fioriFiori draft handling and UI-facing behaviour for CAP services
Signals
none

Content1

Group by
Piece, what it offers
Draft handling1
Keep the Core Clean with Rizing CDSX
SAP Community, Jhodel Cailan, Blog
@rizing/cds-extension1
Keep the Core Clean with Rizing CDSX
SAP Community, Jhodel Cailan, Blog

Seen working5

ArtifactSignals
Samples5
bookshop-demoSimple CDS bookshop model used across CAP explanations
No license
cap-defaultvalue-functionCommon.DefaultValuesFunction pointed at a CAP service function
none
cap-fe-masseditMass edit enabled in a Fiori elements list report over CAP
none
fiori-inline-editList report inline edit on a draft-enabled CAP service
No license
SAP-samples/ui5-cap-event-appEvent registration app showing OData V4 draft with UI5 and CAP
none

Details

Coverage
statecore and community, CAP, Node.js, derived
domainUI & Frontend Bridge
For your agent
Ref
capability:draft-handling
JSON
/capabilities/draft-handling.json
MCP
Connecting an agent