Consolidated Module Views
A guide for administrators on configuring a Consolidated Module View. Learn how to aggregate records from all forms within a module into a single, unified list and customise its columns and behaviour.
What is the 'All Forms' View?
The 'All Forms' View is a powerful feature that can be enabled in any module. It allows users to see records from all different forms within that module in a single, consolidated record list. This is particularly useful for modules like Inspections, where many different inspection checklist forms might exist, and a user wants to see all completed inspections in one place.
By default, the 'All Forms' view includes the following columns:
- Module
- Module Form
- Doc #
- Status
- Accountable Person (Sourced from the person responsible for notification badges)
- Hierarchy Levels (e.g., Site, Department)
This guide explains how an Administrator can enable and customize this view.
Setup and Configuration
Where to find the settings
- Navigate to the Administration area from the main menu.
- Select the Form/Workflow Definition tab.
- Look for the Configure All Forms Button and select it to begin.
How to Configure
The configuration is split into three main areas: Columns, Column Field Mapping, and Other Settings.
1. Defining Custom Columns
The first screen allows you to define custom columns that will appear in the 'All Forms' view.
- Create a Column: Give the column a Name (e.g., "Date of Inspection") and choose the Field Type (e.g.,
datefield
) that will be allowed to map to this column. - Ordering Columns: Use the Weight field to control the order of your custom columns. Columns with a lower weight appear further to the left. These custom columns will always appear to the left of the default columns.
In the example above, we've created a column named "Date" which can only have date fields mapped to it.
2. Mapping Fields to Columns
The second screen is where you map specific fields from your various forms to the custom columns you just created.
- Select the Column you want to map fields to.
- You can map fields in two ways:
- Field Reference: This allows you to map a specific field from a single, specific form. For example, you could map the "Inspection Date" field from the "Workshop Safety Check" form to your "Date" column.
- Name Mapping: This is a powerful time-saver. If you have a consistently named field across multiple forms (e.g., every form has a field named "Brief Description"), you can use name mapping. Simply enter "Brief Description" as the value, and the system will map that field from any form where it exists to your custom column. This avoids having to map each form individually.
Important: You can only map fields of the same type to a column. For example, a column defined as a datefield
type can only have date fields mapped to it.
3. Other Settings
The final screen contains additional settings to control the view's behavior:
- Default View: You can set the 'All Forms' view to be the first view a user sees when they enter the module, effectively making it the default view for that module.
- Display Accountable Column: You can choose whether to display the default "Accountable Person" column.
Version: 1
Record List Configuration
Explains how to configure the fields displayed in a module's record list, allowing administrators to set default and optional fields for user views.
Calendar View
Describes how to enable and configure a calendar view for modules, allowing records to be displayed based on a selected date field and caption.