Records views

Detailed explanation of settings available for record views.

Record views enable you to display the content of a record. You can specify which fields are shown, override default display options, and indicate which actions can be performed, among other things.


This represents a human-readable name for the view. You can utilize spaces, special characters, and a mixture of upper and lower case letters.

This label will appear at the top of the grid view, so ensure you choose something that users will readily comprehend.


This serves as the internal name of the view. It must exclude special characters and spaces.

Typically, you’ll employ the view name in scripts and the REST API. Changing it might impact your app, necessitating manual adjustments.


This designates the entity that the view will be associated with. Only records from this entity can be displayed within the view.


The type specifies the purpose of the record view. The available options are:

  • Read only: In this scenario, the view won’t include editable fields (they will be restricted to read-only). Nonetheless, this type of record view is the only one that supports executing actions on the record (actions like edit or create views cannot be executed). Consequently, when this feature is enabled, the “Main menu” option becomes accessible, offering these choices:
    • All: All action views available in the entity will be presented in the context menu.
    • Some: A personalized selection of actions will be available. A new selector, “Available actions,” will emerge. This selector can be used to pick the actions that will be listed (you choose the action views here).
    • Custom menu: Developers can customize how actions are displayed using this option. Actions can be organized into groups. At the root level, groups will be showcased as dropdown buttons, while nested groups will form nested dropdowns. Several options are available to configure button behavior during runtime:
      • Label: Applicable to Groups only. Groups can include a label.
      • Default options: If this flag is set to false, it permits overriding certain action view configurations.
        • Only icon: Applicable to root-level elements. Buttons can be displayed solely with an icon.
        • Icon: Overrides the predefined icon for the action. If left empty, the icon won’t be overridden.
        • Style: Overrides the predefined style of the action. If left empty, the style won’t be overridden.
        • Label of action: Overrides the action’s label. If left empty, the label won’t be overridden.
    • System Actions Only: Only system actions such as CRUD, Import, Refresh, etc., will be presented.
    • None: No actions will be available.
  • Create: Allows the creation of a new record. In this case, fields can be editable (you can also have read-only fields), and buttons to create the record or cancel the action will be available.
  • Edit: Permits the modification of an existing record. You can have both editable and read-only fields, and buttons to save or cancel the changes will be provided.


Enabling this feature results in new fields added to the entity being automatically added to the view.

By default, this flag is set, as it greatly facilitates development, eliminating the need to be overly concerned with views and allowing you to focus on the model.

Disabling this feature means you need to manually handle the addition of new fields. Changes to or deletion of fields in the entity will still propagate to the view, but new fields must be managed manually.

Show refresh button

Displays a Refresh button, which enables refreshing record data without needing to reload the entire page.

This flag is enabled by default.

Automatic refresh

When enabled, a dynamic listener will be established to facilitate the automatic refreshing of this view for all users whenever a record belonging to the entity associated with this view is updated—whether the event is initiated by a user or a script. This configuration option will be accessible only if the parent collection view (grid or card) hasn’t already enabled this feature or if there is no parent view.

Alert for unsaved changes

Enabling this flag triggers a user message whenever an attempt is made to leave the form after modifying a field. Leaving the form with unsaved changes without encountering the warning is only possible using the cancel button. The message offers the choice to proceed with the record edit or discard changes and proceed with navigation. This feature is functional for both create and edit views and is enabled by default.

Form layout

Allows the definition of how labels and fields are presented on the form. Options include Horizontal, where the label is positioned to the left of the input field, or Vertical, where the label appears above the field.


This represents the list of fields to be displayed in the view. It is possible to sort, remove unnecessary fields, and more.

At this point, you can override default display options. For further details, consult the documentation on General Display Options.


Events permit customization of the UI’s behavior.

These events only apply to the view. Consequently, they are triggered only when interacting with the app through the UI and not via the REST API.

Before show

This event is triggered before presenting the record to the user. For instance, you could effect changes to the record or log that the user accessed the record before its display.

NameTypeDescription is the record that will be shown in the view. Any modifications you make here will be reflected in the UI. You don’t need to explicitly save these changes; they will be applied instantly. However, if you choose to save these changes, they will become permanent.
// suggests a new value for a field'attempt to set a task as urgent');

After create

This event is triggered after a user successfully creates a record. This can be valuable in scenarios where it’s necessary to navigate to another view or display a custom message.

NameTypeDescription is the record that will be shown in the view. Any modifications you make here will be reflected in the UI. You don’t need to explicitly save these changes; they will be applied instantly. However, if you choose to save these changes, they will become permanent.
// logs message and navigate to other view'Record '+record.field('name').val()+' created successfully');
      scope: 'global',
      name: 'navigate',
      view: 'dashboard'

On record change

This event is triggered whenever a field’s value changes. For instance, you could apply alterations to a record field based on the value of another field.

NameTypeDescription is the record that will be displayed in the view. You can make changes to it and they will be applied in the UI. You don’t need to save those changes. If you do, those changes will be made permanent.
modifiedFieldstringThis is the field path that fires the record refresh in the view.
// suggests a new value for a field
if (!record.field('myLabel').isEmpty() && record.field('name').isEmpty()) {
  record.field('name').val(record.field('myLabel').val());'Since name is empty and myLabel is not, we will set the value using the one from myLabel field: ' + record.field('myLabel'));

After save

This event is triggered after a user successfully saves a record. For instance, this event can be utilized to navigate to a different view or display a message.

NameTypeDescription record from the view.
// logs message and navigate to the dashboard view'Record '+record.field('name').val()+' saved successfully');
      scope: 'global',
      name: 'navigate',
      view: 'dashboard'


Permissions allow you to define which groups can access this view.

Permissions for a view can be managed directly within the view definition. However, this approach is just an alternate way of configuring permissions compared to using groups. It is designed to provide an easy means of configuring permissions for the view across all existing groups.

When a new view is created, if a group has permissions to access the entity associated with that view, the view automatically inherits permission for use within that group.

For detailed information about permissions, please consult the Groups documentation.