The Generated Application

When you click Open Application after creation, or access the application URL directly, users arrive at a fully working system. This section covers what the generated application looks like and how to navigate it.

Each application has its own branded login screen. It shows:

The application logo alongside the application name (e.g. “Internal CRM Portal”)
A username field (email address format)
A password field with show/hide toggle
A Remember me checkbox
A Forgot password link
A Log in button

The login screen is styled using the theme chosen during Step 3 of the creation wizard - accent colours, button styles, and the overall visual tone reflect the template applied.

Users log in with their Anybuild credentials. Access to the application and its data is governed by the security roles configured in the Designer.

Application Layout

Once logged in, the application uses a consistent two-region layout:

Top bar

Runs across the full width of the screen. Contains:

The application logo (collapsed variant) on the left
A sidebar toggle button to expand or collapse the left navigation
The logged-in user’s name and avatar on the right

The primary navigation for the application. Each item shows an icon and a label corresponding to the entities and pages in the application. The sidebar can be collapsed to show icons only, which is useful on smaller screens or when more horizontal space is needed for content.

The navigation items and their order reflect the Main Menu Structure defined in Step 4 of the creation wizard. They can be changed at any time from the Designer.

Content area

The main area of the screen, to the right of the sidebar. This is where lists, forms, and detail views are displayed. The content area uses a tab strip at the top - each open section appears as a tab, making it easy to switch between areas of the application without losing context.

List Views

Clicking any navigation item opens the list view for that entity. The list view shows:

Header area

Entity name as a heading
A short description of what the entity represents (editable in the Designer)
Action buttons: + New [Entity], Delete, and a ? help button

Data grid

Each record appears as a row
Columns correspond to the key fields of the entity
Column headers have sort controls
A checkbox on the left of each row allows bulk selection
Selected rows are highlighted
Columns can be scrolled horizontally if there are more than fit on screen

The list view is the starting point for all record management - finding, creating, and deleting records.

Creating a New Record

Clicking + New [Entity] opens a slide-in panel from the right side of the screen. The list view remains visible behind it.

The panel contains:

A title (“New [Entity]”)
A close button (×) in the top right
All the fields defined for the entity, in a single-column form layout
A Save button in the bottom right, styled in the application’s accent colour

Field types in the form

Text fields - plain text input

Number fields - numeric input

Date fields - date picker with a calendar icon

Reference fields (lookups) - show a “Type here to Search” input with search and add icons. Start typing to search existing records. The + icon opens a quick-create form for the referenced entity without leaving the current form.

Status fields - display the current status value as plain text (e.g. “Cold”, “Draft”)

Custom attributes - a structured JSON editor with syntax highlighting and line numbers. Used for flexible, capture-time metadata where the fields are not known in advance.

After filling in the required fields, click Save. The record is created and appears in the list view behind the panel. The panel closes automatically.

Record Detail View

Clicking on a row in the list view opens the full record detail view. This is a dedicated page, not a panel.

Record header

The header area contains:

A breadcrumb link back to the list (e.g. ”← Leads”)
The record identifier (e.g. “Lead: henry@example.com”) with a copy icon
A status badge showing the current record state and version (e.g. “Draft / Version 1”)
Action buttons: + New [Entity], Submit, Clone, Delete, ?

Record status and versioning

Every record in Anybuild moves through a defined lifecycle:

Status	Meaning
Draft	Record has been saved but not yet submitted for review
Submitted	Record has been submitted and is pending approval or activation
Live	Record is active and in use
History	Record has been superseded by a newer version
Deleted	Record has been soft-deleted

The Submit button (shown in green) moves a Draft record to Submitted status. This is visible and prominent in the record header, making the workflow clear to users.

The version number increments each time a record is submitted and approved. This provides a full audit history of how the record changed over time.

Tabs

Below the header, records are organised into tabs. The first tab contains the main entity fields. Additional tabs correspond to sub-entities (components) defined in the data model - for example, a Lead record has tabs for Lead Email and Lead Phone, where multiple email addresses or phone numbers can be stored.

Clicking a tab switches the content area to show that component’s fields or list.

Form layout

The main record form uses a two-column layout by default, with fields arranged in labelled pairs. Each field is directly editable - click into any field to modify the value.

Reference fields in the detail view show the same search and add controls as in the creation panel. The × icon next to a selected reference clears the value.

Navigating Between Records

The breadcrumb in the record header always provides a one-click route back to the list view. The tab strip at the top of the content area shows all currently open sections, so switching between a list and a detail view - or between two different entity lists - is quick without losing place.

What Is Configured vs What Is Generated

Everything described in this section is generated automatically by the platform from the data model. No manual UI configuration is required to get a working application.

Generated automatically:

The login screen (branded with application name and logos)
The sidebar navigation (from the menu structure)
List views with sortable columns for every entity
Slide-in creation panels for every entity
Full detail views with two-column form layout
Tabs for sub-entities (components)
Draft/Submit status workflow on every record
Record versioning

Changeable in the Designer after generation:

Field layout and arrangement (grid customisation)
Which fields appear in list view columns
Additional tabs and drill-down views
Custom forms replacing the generated layout
Help text per entity and per field
Navigation order and icons