Introducing the Cloud Application Programming Model (CAP)
SAP's own general-availability announcement for CAP, laid out as a Golden Path: a data model and service defined in CDS gets a generated service provider that serves metadata publishingMetadata publishingDescribing a service to something other than a human — service metadata for clients, and machine-readable descriptions for registries and discovery.SAP and community, narrow by design and CRUD requests, fills in primary keys and audit data, and writes trace and audit logsAudit loggingRecording who touched personal or sensitive data, in a form an auditor accepts, without hand-writing it in every handler. It is often confused with application logging, which records what the code did rather than who accessed what.SAP only without application code. The same CDS model carries annotations that translate to OData vocabularies and generate a Fiori elements app skeleton, which is how Fiori annotationsFiori annotationsDescribing a service so a Fiori client can render it without hand-written UI code — titles, value helps, hierarchies and visibility expressed as model annotations rather than screen logic.SAP and community, unassessed work in CAP.
Where it sits
Who is behind it
Before you read it
ApplicabilityCore changedFiori annotations changed in @sap/cds-dk 9.6.0, 2025-12-17.
This is a derived prompt to re-check the work, not a claim that the work is wrong. Exact stale statements are recorded separately after editorial review.
Properties
About this work
For audit-logging
For fiori-annotations
Details
Graph
Source
History
- Entered the atlasDiscovered via SAP Community · cap-tag.
For your agent
- Ref
content:introducing-the-cloud-application-programming-model-cap- JSON
- /content/introducing-the-cloud-application-programming-model-cap.json
- MCP
- Connecting an agent