-
-
-
- Configure the HTML editor
- Building blocks for user interface functionality
- Layouts
- Sections
- Defining the columns of a table
- Forms
- Form filters
- Searching for data
- Queries: Introduction
- Queries: Advanced search
- Queries: Columns in table
- Cross tables
- Queries: Saving and opening reports
- Dashboards
- Drop down menu
- Custom (user friendly) URLs
- How to change standard messages and labels
- Tree layout
- Velocity forms
-
Sections
A section defines, among others:
- a title
- a header
- fields to display
- a connected table
- a footer
You can show fields in your section that are owned by the class, but you can also show fields of related classes, defined by a relation in your data model (see "Relations between classes").
You can show one connected table in a section (also according to a relation defined in your data model)
Connected table in a section
The connected table in a section can be customized in a number of ways:
- How and if the details view of records can be opened
- If and how the table is grouped
- What records are displayed through use of a filter (learn more about filters here)
- If and how new records are added to and deleted from the table
- What columns are displayed in the table (learn more about setting columns of a table here)
- What actions are accessible (learn more about actions here)
Presentation
Sections can be presented in different ways with the property "Presentation".
The most common presentations are "paragraph" (see image above) and "tab" (default, see image below).
Section visibility
Fields that are not part of a Section will be shown at the top of the screen above the sections. This behaviour can be changed by setting the 'Show fields that are not on a section' property.
Otherwise section visibility to different user groups can be set in the 'Visibility' tab. A filter can be added for more fine-grained control.
Note that hiding fields through the use of layouts is different than setting permissions. This means that, although not visible, the field will still:
- Be visible when exported
- Be accessible through a REST-API
- Be searchable, if the field is a secondary search field