Getting Started
Quickstart: build your first object
Create an object, design its form schema, add records, publish an action, and place it on a page.
Quickstart: build your first object
This quickstart walks through the configurator on-ramp: create an object, add form fields, create records, add a quick action, and expose the object on a page. Use it for simple internal processes such as site inspections, vendor requests, client onboarding, equipment checks, or incident reports.
1. Create the object
Open the Objects settings area and create a new object. Give it a singular label, plural label, description, and namespace-friendly name. Keep the label business-facing, for example Inspection, Vendor Request, or Customer Onboarding.
Choose the storage engine before saving. Antly supports relational records for normal business workflows and a high-performance NoSQL engine for large-volume dynamic data. The storage engine cannot be changed after creation, so choose conservatively.
2. Build the form schema
Add sections that match how users think about the work. For an inspection object, sections might be Site details, Checklist, Photos, and Outcome. Add questions with clear aliases because aliases are used by reports, filters, scripts, and Page Builder runtime code.
| Field type | Good use |
|---|---|
| Text and textarea | Names, summaries, notes, and descriptions. |
| Select and multiselect | Controlled status, category, region, and priority values. |
| Date and datetime | Due dates, inspection dates, appointment times, and SLA anchors. |
| File and image | Photos, evidence, signed documents, and attachments. |
| Number and currency | Quantities, scores, prices, and totals. |
3. Create test records
Open the object list and add two or three records. Check the table columns, object filter, created-by and created-at display, image display, and detail view. Use table settings to decide whether users need edit, delete, archive, object filter, or image actions in the list.
4. Add a quick action
Create a quick action when users need a repeatable button, such as Mark as reviewed, Send for approval, or Create follow-up task. Give the action a clear label and test it from a record before you rely on it in production.
5. Add a page or menu entry
Feature the object in the menu or add it to a Page Builder page. For staff-only access, place it in the main workspace. For customers, enable customer settings and place it in the portal menu. For anonymous submissions, enable a public form and use /form/<code>.