When you configure a mobile form, you can choose to have version numbering, so that different versions of the same form have different numbers. If you enter a Root Code and leave the actual Code field blank, when you save the form configuration, the actual code is auto generated by adding a version number to the root. The version number starts at 001 and each time you add a new form with the same root code, or copy the form, the version number increases by 1. If you copy a form and amend the root it will create version 001 of a new form.

You need to specify the type of the Mobile Form, which is where it can be used.

Typically forms would have a single type, but a form can be used for more than one type of record (for example, contracts and health and safety). Certain features are form type specific and would be unavailable to a multi-type form.

When you tick the Live box on the form, it will make it available on the mForms app.

If a form is type H&S Audit, Coins ERP+ creates menu entries on the H&S Audit menu for the audit workbench and report.

The serial number is the number that is assigned to each instance of a form as it is entered. This can be a simple numeric format; for example, "999999". It can contain a fixed string followed by a variable numeric format; for example, "ABC[99999]". It can contain a range of numbers; for example, "ABC[00123-04567]" will start with the first serial number being "ABC00123" and will continue up to "ABC04567".

This allows you to use Page Designer to create your own version of the form if you want something different to what is automatically generated on Coins ERP+. On the KCO form we have created a page KCO001 to lay out the form.

When defining your own page there is a certain amount of repetition – you need to specify the labels both on the page and on the form for example – as it is not being done automatically, but it does give great flexibility and control.

The RW_smk_field^ with a parameter of a pipe separated list of the section, element and field sequence numbers is used for values. You can use data type specifics by adding a suffix – e.g. RW_smk_fieldDE^ for decimal. Other suffix options are: DA for date, IN for integer and LO for logical.

There is an optional fourth entry to the parameter which can be sme_text for the field comments or sme_xlist for the checklist.

There is a similar RW_smk_workflow^ for workflows.

You can override the default number of column spans used in the ERP+ view of the form. This defaults to 12 spans (4 for label, 8 for data). You can use this to get a better distribution of the fields without needing to set the column and label spans on all fields.

The mock-up below shows how two fields with no override would be laid out. The second span is forced to expand to accommodate the width of the combo box of the first field, meaning other spans get less of a share. The label for this field is forced to wrap text to fit in its span. The second field comes on a new row as append was not set and we get wasted space to the right of the fields.

The mock-up below shows how a 12 span page with 4 label spans will lay out fields. The section title uses all spans, and the automatically added fields use the label spans, provided there are enough remaining spans for what we need to include. The 2 fields in this section both have 4 label spans defined and value 2 in Cols, and the second field has Append set to true.

Either all users can enter the form, or you can nominate a group that the user must have access to view, edit and submit.

When updating an existing Completed Mobile Form, the users will be able to view the details of all the Mobile Forms available to their group.

They will only be able to edit them if their Prime Group is the same as the Prime Group on the completed mobile form, and their security level is greater than the security level on the mobile form.

There is a system parameter SY/EQACCESS that allows users in the same group and with the same security level to edit each other’s forms if set to Y.

Summary of the behaviour on the apps:

For advance use: the next table shows the conditions which allow you to view and update mobile forms:

Select the default document form to use print this form. (When printing the form, users can select a different document.)

Documents are set up using Reporting and BI > Document Designer > Document Designer with Type ‘Mobile Form Print’.

Email subject for automatic prints that are circulated. If blank, a default is used. You can include fields from the available (submitted) forms by using curly brackets. For example {jc_job} {su-userid}