Objects
Objects overview
Use Antly objects as configurable business data models for staff, portal, and public workflows.
Objects overview
Objects are Antly's dynamic-data engine. An object defines a business entity, its form schema, record list, detail view, associations, pipelines, reports, scripts, workflows, and exposure rules. Antly stores each object with a tenant, namespace, labels, settings, public flags, customer flags, static links, and a storage engine.
Object types
| Type | Use for | Visibility |
|---|---|---|
| Staff object | Internal operational data such as inspections, cases, assets, requests, or registers. | Main workspace, controlled by roles and menus. |
| Portal object | Customer-visible data where signed-in customers can view or create their own records. | Customer portal, controlled by customer settings. |
| Public object | Anonymous submissions through /form/<code>. | Public web form with explicit public flag and code. |
| Static-linked object | Object that links to built-in surfaces such as notes, files, tickets, tasks, bookings, or assets. | Record detail tabs and associations. |
| ERP module object | Module-provided object installed through tenant apps. | Module app and launchpad permissions. |
Configure an object
- Create the object with a stable label, plural label, namespace, description, and storage engine.
- Build the form schema using sections and questions.
- Configure table, detail, filter, customer, public, child, and automation settings.
- Add pipelines, quick actions, scripts, workflows, and reports as needed.
- Place the object in menus, pages, portal layouts, or public forms.
Operating guidance
Do not rename namespaces after an object is in use. The backend prevents namespace and storage-engine changes because scripts, reports, permissions, workflow payloads, and API integrations may depend on them. Use labels for user-facing wording changes and keep namespaces stable for integrations.