This release gives administrators more control over the structure and behaviour of Custom HTML Forms. Large forms can be organised into tabs, child forms can be placed where they are needed, child document forms have their own controls, and complete modules can be rebuilt from their saved definitions.
Custom Form Builder and API
- Place Child Forms where they belong: The Child Forms builder field lets you choose one or more child forms and place them between normal fields instead of loading every child form at the bottom.
- Organise forms with tabs: Each field can have an optional tab name. Fields with the same tab name appear together; fields without a tab remain in the normal form layout.
- Control tab order and placement: Tab group and sequence settings define the order of tabs and where each group appears among normal fields.
- Use tabs in child forms: Child forms support their own tab, group and sequence settings without changing the parent layout.
- Consistent generated pages: Add, Edit and View pages use the configured tabs and child-form layout. Child-form titles appear above their tables, and forms sharing a position are grouped as tabs.
- Better row validation: New rows are added to the correct child table. Empty child rows are ignored; started rows validate required fields and identify the affected tab.
- Compatible upgrade path: Existing forms keep their current layout until an administrator chooses to recreate them.
Child Document Forms and Module Rebuild
- Child Document Forms: A separate document and form can be linked to a parent document. This differs from a Child Form, which stores repeatable rows within the parent form.
- Related records: Existing child-document records appear on the parent form’s Edit page. New records are added from the parent View page.
- Dedicated configuration: Available child-document forms are listed with table name, version, status and an action to open the form.
- Rebuild the full module: Rebuild Module regenerates the main form, every Child Form and every Child Document Form from their saved JSON definitions.
- Preserve existing work: The rebuild keeps configured fields, tab settings, links, table settings and existing records.
Application Tab Configuration
- Central controls: The configuration page lists tabs from the main form and linked child forms.
- Visibility by action: A tab can remain visible, hide on Add, hide on Edit, or hide on both.
- Visibility by field value: A tab can appear only when a selected radio or dropdown field contains one of the chosen values.
- Independent child controls: Each child form keeps its own visibility settings, avoiding empty parent tabs when child content is hidden.
- Clear validation feedback: If a started child row is incomplete, its related tab is highlighted in red. Unused empty rows do not trigger an error.
- Available to every custom module: These settings work with any custom form that uses tabs or linked child tables.
Improved Custom Table Configuration
- Configuration tabs now use Main Form and Child Forms instead of Main Table and Child Tables.
- Configuration content loads when its tab is selected, keeping large module pages responsive.
- Data Entry, Table Permissions, Charts and Panels, Email Triggers, Create Tasks and Add JavaScript remain available as focused sections.
- Enhanced form controls are reinitialised when their configuration tab loads.
Required Database Update
Add the nullable tab_settings column before using Tab Configuration. Existing forms are unaffected until tab settings are saved.
ALTER TABLE custom_tables ADD tab_settings TEXT NULL;