Custom modules and fields: turn the platform into the exact vertical product

Each module receives a stable key, label, configuration, tenant context, and relationship to its pages and components.

A custom business object participates in security, activity history, files, conversations, tasks, calendar, AI, and workflow through its shared RecordId.

The system stores custom work items and field values while preserving the module and tenant boundaries.

Custom records can connect to contacts, users, locations, files, tasks, workflows, and other records.

Fields define a data type, label, stable key, default value, option set, display group, and ordering.

Required state, regular expressions, minimum and maximum values, maximum length, and option metadata can be applied centrally.

Field metadata declares whether values participate in searching, sorting, filtering, and list presentation.

Sensitive values can be hidden, encrypted, and revealed only through an authorized, audited operation.

A customer can extend or reshape its own module without changing the base application used by other tenants.

Page JSON binds components to module data, fields, actions, and APIs.

Components can respond to user roles while backend authorization remains the final security authority.

Field changes, button actions, record creation, approvals, schedules, and external events can enter the workflow engine.

Custom logic can run in an isolated extension and return structured results to the page or workflow.

Create patient programs, care plans, authorizations, assessments, facility records, and clinical workflows.

Create locations, compliance inspections, royalties, vendors, campaigns, and regional scorecards.

Create matters, engagements, trust records, milestones, deliverables, time entries, and approvals.