Capture a custom record's change history at commit
What It Does
Database capture attributes business changes at commit, including changes made through cross-service functions. History presentation later applies current definition and readership filtering.
The Flow
When Something Fails
Fail commit and roll back the complete mutation. The record and revision remain atomic. Fail the changing transaction if deferred capture cannot settle. The connection change cannot commit without its revision. Reject commit if this trigger fails. Mutation and revision roll back together. Return not found when object or required record reach is unavailable. History storage is unchanged by a refused read.
Open Design Questions
Native-record timeline presentation needs an agreement with CRM.