Sections are essentially screens or pages on the mobile app. Within each section, you will define the fields that appear for the end user to capture information.
Sections Tab
ID
Sequence numbers are now shown for sections. These values can be used with RO fields to access values of a completed mobile form.
Title
The title of this section.
Type
The type of section is either "Normal" or "Table".
The "Normal" type means that fields within this section will only be entered on mForm once. Useful for simple forms to produce simple reports.
The "Table" type means that each field within a section can be entered multiple times for different Section Element questions, creating a table of answers. (For example, if inputting score values for different KPIs in a single site audit without having multiple sections/screens per KPI).
This is useful for more complicated forms where intelligent reports or calculations are needed without impacting user experience of mForms.
DB Table
If this field is set, the data will be linked to a Coins ERP+ database table.
This can now have a value of “sy_mobfel” which you can use to create multiple repeats of the same section. When sy_mobfel is entered you get a link to maintenance of the section elements.
Table View
This will work only if the Type was set as Table and if the Section Elements are defined.
Presentation style of the DB Table:
SELECT - choose a record (Section Element question) at top of mForms screen.
ROW - an update row per record (Section Element question). There is a limit of columns available on the mobile devices.
MAINTENACE - browse records with add/update option going to standard maintenance screen. Inspect option to enter form details.
Starting Section
Indicates if this is the starting section of the Mobile Form. One and only one section must be marked as the starting section.
Next Section
This field indicates which section should be shown next after the questions on this section have been completed.
Error Section
This field indicates which section to go to next, rather than the standard next section, if an invalid answer is entered on any of the fields within this section.
You could use this, for example, to prompt the user to capture the issue and complete the inspection immediately if there is a high risk to them if they continue.
Retired
If this field is set it indicates that this Section is no longer in use. If there are existing answers recorded against this Section, it will not be possible to delete it; instead it can be marked as retired.
Workflows
This field allows you to specify the number of user triggered workflows available on a Section. These are different from dynamic workflows and are set to allow end users to select from a list of active workflows to meet specific business needs.
On the mForms app the workflows selection will appear at the end of each Section where users will need to insert comments and optionally add due by date during the process of completing mobile form.
For example, workflows are used in the Health & Safety Auditing process where tasks are created in the H&S Action Monitor.
Workflow for Action Monitor should be designed to create Tasks with $hev_type='HSAUD';
Images
Allow images to be included on this section if enabled.
The mForms app allows the user to add images that they can capture or attach from gallery. These images are annotatable and are stored against the sy_mobcform document category.
Hide When Status
A can-do list of statuses that prevent the whole section from appearing. Use the pseudo status NEW to denote a new form with initial blank status.
This only applies when updating the form in Coins ERP+.
Read Only Statuses
A can-do list of statuses that prevent update of the section’s fields. This is the default action for fields of the section; you can override this on individual fields which have their own can-do list.
This only applies when updating the form in Coins ERP+. Restricting the fields that are updatable in Coins ERP+ gives a better user experience because users do not need to tab through fields they don’t need to change, and because a reduced input field count gives a faster performing page.