Custom Record
What It Models
A custom record is one entry in an organization’s register. It combines typed property values with a derived number and name, optional publication, attachments, links and retained revisions.
Identity and Attributes
Creation fixes record identity before attachments are prepared. The object’s definitions determine validation and naming; archival retains content, while deletion removes record data and preserves history.
Relationships
The parent controls ordinary write availability, properties govern values, and Associations owns the links that influence deletion.
Invariants
Record saves apply current rules and concurrency checks. Supported mutations commit audit, history and events together, and deletion follows relationship safeguards within one transaction.
How It Is Stored and Shared
Custom Objects owns the shared record and value store. Queries reads it through granted interfaces; endpoint functions let CRM apply transactional deletion and merge effects. The event queue handles delivery after commit.
Open Design Questions
Platform’s asset cleanup is absent, leaving abandoned or detached copies. Per-owner limits and HTML processing are separate unresolved planning issues.