Entity Builder Overview
Entity Builder is the foundational data layer of AutoBridge. It lets administrators define custom data structures — entities, fields, forms, and views — without writing code. Every module in AutoBridge, from Permitting to Constituent Manager, is built on top of Entity Builder.
What is Entity Builder?
An entity is a structured data record type. Examples include Permit, Inspection, Contractor, Property, Case, and Service Request. Entity Builder lets you define what fields those records contain, how they are validated, how they relate to each other, and how they are displayed to staff and citizens.
Think of Entity Builder as a configuration layer that replaces what would otherwise require database schema changes and developer work. Non-technical administrators can define and modify data structures through a visual interface, and changes take effect immediately across all forms and views that use those entities.
Core Capabilities
Entity & Field Definition
Create named entity types and add fields of any supported type. Each field has a label, data type, validation rules, and display options. Field types include:
| Type | Use |
|---|---|
| Text | Names, descriptions, notes |
| Number | Quantities, fees, counts |
| Date / DateTime | Deadlines, submission dates, scheduled times |
| Dropdown | Status, category, type selections |
| Lookup | Reference to another entity |
| Checkbox | Boolean flags |
| File | Document attachments |
| Calculated | Derived values from other fields |
Form Builder
Arrange fields into intake forms used on the Constituent Portal or internal staff-facing entry screens. Forms support conditional logic — fields can show, hide, or become required based on other field values.
Views & Filters
Define list views that staff use to browse and manage records. Control which columns appear, default sort order, and available filters. Views can be role-specific so different staff groups see different default perspectives on the same data.
Relationships & Lookups
Link entities together to model real-world relationships. A Permit record can look up a Property record. An Inspection can reference a Permit. Lookups are navigable — staff can jump between related records without leaving context.
Versioning
Field and entity changes are tracked. Administrators can review what changed, when, and who made the change, supporting the audit requirements of government operations.
How It Fits in AutoBridge
Entity Builder is not user-facing on its own. Its output — the entities, forms, and views it defines — powers every other part of the platform.
| Module | Uses Entity Builder For |
|---|---|
| Permitting Solution | Permit type definitions, inspection records, contractor records |
| Constituent Portal | Service request forms and intake data structures |
| Automation Builder | Trigger conditions based on entity field values |
| Calendar & Scheduling | Appointment types and associated record links |
When to Use Entity Builder
- Adding a new permit type with custom fields
- Creating a new service category on the Constituent Portal
- Adding a required field to an existing record type
- Defining a lookup relationship between two record types
- Changing validation rules on an existing field
Note
Changes to entity definitions affect all forms and views that use that entity. Test changes in a non-production environment before applying to live data.
Next Steps
Documentation in Progress
Detailed guides for entity creation, field types, form builder, views, and relationships are being developed. Check back soon.