Change tracking
Keeping a readable history of what changed on a record, who changed it and when — as business history rather than database journalling.
Overview
@cap-js/change-tracking Out-of-the-box change history for annotated entities.
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.
Not covered: It stops at personal data: both packages skip elements annotated with @PersonalData, which are subject to audit loggingAudit 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, and the Node.js README gives the reason, that a readable log would let users get around the audit log. On Java, changes made through native SQL, JDBC or a remote service are not tracked, and the retention of the log and the access rules on it are the application's to settle.
Artifacts
Content
Details
Coverage
For your agent
- Ref
capability:change-tracking- JSON
- /capabilities/change-tracking.json
- MCP
- Connecting an agent