schema – forms workspace

  • Updated

The Forms workspace is the operational environment where admins design, manage, and maintain Forms based on the data model.

While the Data workspace defines what information exists, the Forms workspace establishes how that information is presented and captured. This workspace allows admins to project objects, fields, and relationships into structured, user-facing Forms without altering the underlying data model.

Rather than working with raw data definitions, admins work with configurable interfaces that control layout, visibility, and behavior for end users.

access the forms workspace

Accessing Forms is straightforward:

  1. Log in to Neostella.
  2. Open the Control Center.
  3. Click Schema.
  4. Click Forms.

Once opened, the Forms workspace displays the Form Dashboard, which serves as the starting point for locating existing forms, filtering them, and creating new ones.

4 STEPS

1. To access the Forms workspace, start by logging in to Neostella.

Then, open the Control Center workspace.

2. Click Schema.

3. This opens the Forms workspace.

Once inside, you’ll see the Form dashboard, which serves as the starting point for locating existing forms, applying filters, and creating new forms.

4. That's it. You're done.

https://www.iorad.com/player/2668932/Forms---access-the-forms-workspace?iframeHash=watchsteps-1&lang=en



Next step

forms dashboard

The Forms workspace is designed to support three primary admin activities:

  • Discovery.
  • Creation.
  • Maintenance.

From this single view, admins can review all Forms available in the system, understand how they relate to objects in the data model, and access the Form Editor for configuration. The workspace is composed of the following key elements:

1. Form Filters Menu 

  • Form Name.
  • Object Name.

     

2. ADD NEW FORM button

3. Form Table 

  • Toolbar
  • Name column.
  • Form ID column.
  • Object column.
  • Status column.
  • Creation Date column.
  • Creator column.
  • Last Modified Date column.
  • Last Modifier column.
  • Actions column.

15 STEPS

1. The Forms dashboard is designed to support three primary admin activities: discovery, creation, and maintenance.

From this single view, you can review all forms available in the system.

2. At the top, the Form Filters menu helps you locate forms more easily.
You can filter forms by Form Name or Object Name to narrow the list.

3. The ADD NEW FORM button allows you to create a new form directly from the dashboard.

4. Below, the Forms table displays all forms in the system.

5. The table includes a toolbar.

6. The Name column shows the form’s display name.

7. The Form ID column displays the unique identifier assigned to the form.

8. The Object column indicates which object the form is associated with.

9. The Status column shows whether the form is active or inactive.

10. The Creation Date column displays when the form was originally created.

11. The Creator column identifies the user who created the form.

12. The Last Modified Date column shows the most recent update made to the form.

13. The Last Modifier column indicates who last edited the form.

14. Finally, the Actions column provides access to available actions for managing the form.

15. That's it. You're done.

https://www.iorad.com/player/2668936/Forms---forms-dashboard?iframeHash=watchsteps-1&lang=en



Next step

form filters menu

Form Filters = the fastest way to locate Forms at scale.

As the number of Forms grows, the Filters menu allows admins to quickly narrow results and locate the correct form without scanning the entire table. Forms can be filtered by:

  • Form Name.
  • Object Name.

Filters can be combined to further reduce results and improve search accuracy.

Multiple filters can be applied at the same time (for example, Form Name + Object Name).
Invalid or non-matching values return a No rows message.

ADD NEW FORM button

ADD NEW FORM = entry point to form creation.

This button opens the Form Editor, where admins define the form’s layout, field visibility, and behavior. When creating a new form, the selected Object determines which fields are available, which relationships can be referenced and which object types apply.

This ensures that forms always remain aligned with the underlying data model.

forms table

The Forms Table provides a consolidated view of all forms available in the system. Each row represents a single form and includes contextual information that helps admins understand its purpose, status, and lifecycle. From this table, admins can:

  • Open forms directly in the Form Editor.
  • Review which Object a form is based on.
  • Track creation and modification history.
  • Edit metadata or inactivate Forms when necessary.

forms table columns

Column Type Description Example
Name Informational / Editable Displays the Form name and serves as the direct link to the Form Editor. Intake Specialist | Personal Injury
Form ID Informational Unique identifier assigned to the Form. 0b0614f8-b778-41be-af67-35d3e456f1da
Object Informational Object used as the data foundation for the Form. Project
Status Informational Indicates whether the Form is active or inactive. Active
Creation Date Informational Date the Form was originally created. 1970-01-01T00:00:00.000+00:00
Creator Informational User who created the Form. Ben Schmitt
Last Modified Date Informational Timestamp of the most recent change. 1970-01-01T00:00:00.000+00:00
Last Modifier Informational User who last modified the Form. Samantha Bickley
Actions Edit / Delete Allows editing metadata or deleting the Form entirely. —
The Object Type used by a Form is inherited from the Type tab defined in the Data workspace.

relationship between Forms and Data

Forms do not store or define data themselves. Instead:

  • All fields shown in a Form originate from Objects in Data.
  • Field availability and behavior are governed by Data configuration.
  • Object Types and Relationships determine what information can be displayed or selected.

Because of this dependency:

  • Any change made in the Data workspace may affect existing forms.
  • Forms should always be designed after the data model is finalized.

common use cases for forms

Forms are commonly used to:

  • Capture intake and onboarding information.
  • Display structured case or project records.
  • Update object data during case progression.
  • Support reporting, workflows, and downstream automation.

Since Forms rely on a shared data model, information captured through Forms is immediately reusable across the platform.

Was this article helpful?

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.