System Layer — Shared Services Behind HEPO
Understand HEPO's shared security, data, integration, local AI, workspace, and extension services, and how to evaluate them in your deployment.
Shared Module: configure supported data surfaces
Use shared list, form, and detail patterns for configured records, with explicit schemas, operations, and permissions.
Use shared list, form, and detail patterns for configured records, with explicit schemas, operations, and permissions.
Shared Module provides configurable screens for managing records in HEPO. It supplies reusable lists, forms, detail views, and related presentation patterns, using the configured fields, schemas, and operations for the record type.
This gives implementers a way to reuse the platform's interface behaviour when a business needs another governed data surface. Within the supported configuration path, a separate hand-built screen is unnecessary.
Move a useful record structure into the working model
Consider a logistics company's container-condition records, a clinic's outcome records, or a manufacturer's line-quality records. Each illustrates domain information an organisation may need to structure. These are possible configurations to evaluate with an implementer.
For a container-condition record, the team would identify the required fields, valid values, relationship to a shipment, permitted actions, and viewers. The implementation then establishes whether the shared configuration path supports that record and its operations.
What is supplied and what must be defined
| Shared capability | Configuration or implementation responsibility |
|---|---|
| List and search | Available fields, columns, filters, and supported query operation |
| Create and update | Form schema, field behaviour, validation, and save operation |
| Detail | The information and related context appropriate to the record |
| Permissions | Access rules and the authoritative operations that enforce them |
| Process and dashboard integration | Supported routes, lifecycle behaviour, and selected views |
Configuration can arrive through supported module settings or interpreted definitions. It still needs matching server operations and data handling. A rendered form does not create arbitrary business logic or a database lifecycle by itself.
Fit the three levels of adaptation
Common Canvas arranges existing views. Shared Module configures supported data-management surfaces. Code Factory produces artifacts for a module or capability when the requirement extends beyond that configuration.
The shared patterns help the new surface fit the rest of HEPO. Permissions, validation, relationships, and audit behaviour still need to be configured and verified on its actual operation path. Inheriting an interface pattern is not proof that every required control is present.
Build the first configuration together
Business owners define the record's purpose and responsibilities. Consultants help clarify the fields and relationships that capture the domain. Implementers select the supported configuration path and establish any required underlying operations.
Review a record from creation through search, detail, update, and a denied operation. Check a validation failure and a related record as well. That demonstrates a useful governed surface and identifies where a specialised extension is needed.