Synchronise record-derived responsibilities
What It Does
An application synchronizes the complete holders derived from one record within that record’s transaction.
The Flow
Call the derived synchronization function with application, derivation key and complete desired holder set in the business transaction. Validate actor, ownership, derivable areas, holder, scope, dates and unique area-scope entries, then insert new rows, refresh windows and end omitted rows with audit. Rebuild the uncovered-area report through later reconciliation.
When Something Fails
The database raises on refusal and the application transaction rolls back. A refused synchronization commits no business change. Validation precedes mutation and failure aborts the transaction. No partial desired set commits; ended cover is not separately cleaned here. A failed reconcile waits for another scheduled opportunity. Derived gap reporting and its attention can lag the business change.
Open Design Questions
Effective holder reads exclude ended derived holdings even when attached cover rows remain active.