Merges Service Module
What This Service Is For
The merges module prepares reviewed combinations and executes them as durable attempts. It retains original values and absorbed identities so staff and integrations can explain the result after participant deletion.
Boundary
Plans, attempt history, job records and aliases belong here. Ordinary survivor saves and absorbed deletes call Entities; merge persistence also moves affiliations and references and prepares organization hierarchy. Application-owned functions apply changes outside CRM ownership.
Operations in Words
Type-specific read and merge permission pairs authorize planning and execution. Merge-read authority controls workspace history and aliases, while record-scoped lineage operations use the record’s read authority and selectively expose additional audit detail.
Events and Jobs
Contact merging writes a committed business event; organization merging currently writes none. Participant audit pointers and ordinary record events share the successful transaction. Job reporting begins before execution and maps the outcome to watched steps afterward.
Consistency Guarantees
Business changes are atomic, with failure recorded separately after rollback. Task reporting, announcement delivery and derived projections can lag that outcome. Each operation declares its unpublished Submissions status.