com.sap.cds:cds-feature-change-tracking
Records who changed which annotated field on a CDS entity and when, as a queryable change log for CAP Java, covering every modifying CQN statement but not native SQL or JDBC.
Adds change tracking to a CAP Java service, part of the cds-services-bomcom.sap.cds:cds-services-bomThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, cap release line. It tracks the changes of all modifying operations executed via CQN statements, whether triggered by a protocol adapter or by custom code, and stores each addition, modification or deletion in a flat sap.changelog.Changes entity. Changes made through native SQL, JDBC or anything else that bypasses the CAP Java runtime, or that is forwarded to a remote service, are not tracked. An entity opts in by being extended with the changelog.changeTracked aspect and marking the elements to log with @changelog; the Node.js counterpart, @cap-js/change-tracking@cap-js/change-trackingOut-of-the-box change history for annotated entities.sap official, cap, is documented for the same plugin under its own runtime. The dependency is added to srv/pom.xml with runtime scope, or compile scope when a handler needs to read the change log entries itself.
Facts
Where it sits
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
Connections
Keeping a readable business history of changes to a record
Download
Others providing
Compare all 3 on the Change tracking page →- @cap-js/change-tracking@cap-js/change-trackingOut-of-the-box change history for annotated entities.sap official, capChange history for annotated CAP entitiesfrom CAP
- cdsmbt01cdsmbt01This is CDS plugin that enable OData change tracking for CAP applicationsindependent, capCDS plugin for OData change tracking in CAP applicationsfrom CAP
Details
Sources
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
Flavors
“Changes made through the native SQL, JDBC, or other means that bypass the CAP Java runtime or that are forwarded to the remote services aren't tracked.” — Change Tracking
History in the atlas
- Tracks the changes of all modifying operations executed via CQN statements and stores each addition, modification or deletion in a flat change log entity that a projection can expose on an object page.
- First seen.
For your agent
- Ref
artifact:cap-java-cds-feature-change-tracking- JSON
- /artifacts/cap-java-cds-feature-change-tracking.json
- MCP
- Connecting an agent