schema - forms editor overview

The Form Editor is the central workspace for creating, editing, and managing forms in Neostella.

It is a no-code customization tool that transforms the data structure of an Object into a user-facing form. While the Data workspace defines what information exists (objects, fields, and relationships), the Form Editor defines how that information is captured and presented to users.

The Form Editor links directly to the data model. It does not create or modify data structures; instead, it projects an existing Object into a Form so users can enter, review, and update information through a controlled interface.

This tool is designed for System Managers, Operations Managers, or internal roles responsible for platform configuration, and not for end users.

what the form editor allows to do

Using the Form Editor, admins can:

• Add different field types (text, dropdowns, checkboxes, date fields, file uploads, and more).
• Reorder and group fields.
• Define default values.
• Apply logic (for example, show or hide fields based on user input).
• Connect Forms to workflows, APIs, or automations.
• Preview how the form will appear to end users.

All behavior is driven by the selected Object as the form’s data source.

how to access the form editor

There are three ways to open the Form Editor:

• When creating a new Form

1. Click ADD NEW FORM from the Forms Dashboard.
   The Form Editor opens automatically.
    

• From the Forms table (Name column)

1. Click the name of an existing Form.
   The Form Editor opens automatically.
    

• From the Forms table (Actions column)

1. Click the three-dot menu in the Actions column.
2. Click Edit Form.
   The Form Editor opens  automatically.

Here's an interactive tutorial

https://www.iorad.com/player/2668977/Data---how-to-access-the-form-editor?iframeHash=watchsteps-1&lang=en

Next step

form editor dashboard

The Form Editor dashboard is composed of the following elements:

Here's an interactive tutorial

https://www.iorad.com/player/2668991/Forms----form-editor-dashboard?iframeHash=watchsteps-1&lang=en

Next step

form name field

The Form Name field defines how the form is identified in the forms table.
This name is used by admins to locate, manage, and reference the form. Changing the form name does not affect the underlying Object or data structure.
 

Object Dropdown

The Object dropdown defines the data structure that the form is based on. This selection:

• Determines which fields are available in the Form Editor.
• Establishes the direct connection between the form and the data model.
• Defines where the data entered through the form is stored.

The form acts as an input interface for the selected Object. All fields, relationships, and object types used by the form originate from this Object.

For example, If an administrator creates a form and selects the New Client Object, the form automatically adopts the New Client data structure. Only New Client fields become available in the Form Editor, and any information entered through the form is saved directly to New Client records.

If the Object selection is changed to Intake, the form updates to reflect the Intake data model instead. Different fields become available, and submitted data is now stored on intake records.

This is why the Object dropdown is a critical step when creating a form: it defines what data the form collects and where that data lives in the system.

status dropdown field

The Status field controls whether the form is available for use.

filter menu

The Filter Menu is a utility within the Form Editor that helps admins quickly locate and manage fields when building a form.

The Filter Menu only displays fields that belong to the Object selected in the Object dropdown field. Fields from other objects are not available. 

Available filters: 

• field name filter

Allows users to search for fields by typing part or all of the field name. This is especially useful for objects with a large number of fields.

• field types filter

Displays only fields of a selected type. Common field types include:

• Address
• Date
• Deadline
• Dropdown
• Email
• Merge Field
• Multi-select
• Number
• Period
• Phone
• Radio Button
• Relationship
• Text
• URL
• Yes / No
   

• object types filter

Filters fields based on the Object or data source they originate from. This is useful when a form pulls fields from multiple related objects (for example: Project, Intake, Contact, or Activity).

• limitations filter

Displays fields based on their configuration restrictions. Available options include:

• Archived – Fields that are no longer active or maintained.
• Hidden – Fields that exist but are not visible to end users.
• Locked – Fields that cannot be edited.
• None – Fields with no limitations.

add all from toolbox button

The ADD ALL FROM TOOLBOX button adds all available fields in the toolbox to the form layout. This action depends entirely on the fields exposed by the selected Object.

remove all from toolbox button

The REMOVE ALL FROM TOOLBOX button removes all fields from the form layout. This action only affects the form layout and does not delete or modify the fields in the Data workspace.

designer tab

The Designer tab defines the structure and visual layout of a form and serves as the primary workspace for building it. Admins use the form canvas to add, remove, and arrange fields from the selected object, as well as to set the form name and description.

Within the Designer tab, fields can be organized across one or multiple pages, and each field can be configured individually for labels, visibility, and display settings—without affecting the underlying data model. Layout changes are reflected in real time on the canvas, with undo and redo available to refine the design.

Once the layout is complete, the form can be saved to preserve all visual and structural changes.

preview tab

The Preview tab provides a functional preview of the form as it will appear to end users.

This preview displays the layout created in the Designer tab and allows admins to interact with the form fields as if they were users. Field behavior can be tested safely, including default values, visibility, and interactions between fields.

The Preview tab also responds to any logic configured in the Logic tab. This makes it a safe testing environment where admins can verify that the form behaves as expected without affecting live data or configuration.

This tab is strictly representational and does not modify the form configuration.
 

logic tab

The Logic tab controls the dynamic behavior of the form. From this tab, admins define rules that evaluate user input and trigger actions automatically as the form is filled out. These rules compare field values against conditions such as Equals, Contains, or Is Empty, and then determine what action should occur.

For example, if a user selects USA as their country, the logic rule can enable or display a State field. If the user selects a different country, the same rule can hide, disable, or reset that field.

By using Logic, Forms can guide users through relevant paths, reduce unnecessary fields, and help ensure accurate and complete data entry.
 

JSON tab

The JSON tab displays the technical representation of the form’s configuration in JSON format.

This view reflects the structure, layout, and logic defined in the Designer and Logic tabs. The JSON is generated automatically based on the form settings and is intended for advanced use cases such as debugging, validation, or integration support. This read-only view cannot be modified.