How it works
See when a record was created or updated and which account made the change. Basic metadata helps teams assess the recency and context of operational information.
A concrete business example
Review new requests and records that have not changed recently. Identify where a conversation is needed before assuming the recorded status is current.
How it supports people and agents
If several agents use one service account, capture the actual agent and execution ID separately. Account metadata alone may not identify the actor responsible for the work.
Core scope and boundaries
Modification metadata does not explain intent or capture every external action. It is not a complete cross-system audit trail.
Start with a real case
- Write the business definition and assumptions before creating the calculation.
- Check normal, missing and exceptional inputs with the process owner.
- Label derived indicators clearly and retain a review owner for rule changes.
Core product guide: these pages explain foundational capabilities and configurable application patterns. Integrations and the selected product release require validation. Enterprise automation, fine-grained governance and independent verification are separate scope.