New fields have been added to Mobile Form Maintenance.
Mobile Forms Set Up
Root Code
When adding a new mobile form, you can choose whether to have version control, by entering a Root Code rather than an actual code. When a root code is used the actual code is generated by adding the version number to the root. The version number starts at 1 and each time you add a new form with the same root code the version number will increase by 1. If you copy the form and leave the root code the same it will create a new version of the form. If you copy and amend the root it will create version 1 of a new form.
Type
You need to specify the type of the Mobile Form. Currently this can be either FM or H&S Audit.
Live
If a form is flagged as H&S Audit, when you tick the Live box on the form, menu entries are created on the H&S Audit menu for the audit workbench and report.
Calculation
The calculation is run when the form is submitted. It can be used to set scores or update fields on the form. There is an array of score fields on the submitted form that you can store scores in, and when used the score appears on the audit workbench.
Mobile Form Calculations
To assign a score you assign a variable smk_score__n where n is the array index 1 to 9.
Each field on the form that has a field ID assigned to it will also populate a variable in the calculation, and some new functions have been added to make getting score from these variables easy.
In the example below the form has a number of criteria and each is given an operational and admin score. The operational scores all have field IDs ending OP, and the admin ending AD, so score 1 is the total points for operational, 2 the admin total. Scores 3 & 4 are the percentage – the scores are out of 4 so 25 x average is the same as 100 x average / 4. The varaverage function ignores fields with a blank entry (not applicable).
smk_score__1 = vartotal('*OP');
smk_score__2 = vartotal('*AD');
smk_score__3 = 25 * varaverage('*OP');
smk_score__4 = 25 * varaverage('*AD');
smk_score__5 = if(smk_score__3,GE,90,1,0) + if(smk_score__3,GE,80,1,0) + if(smk_score__3,GE,70,1,0) + 1;
$cRANK = entry$(smk_score__5,'FAIL,BRONZE,SILVER,GOLD',',');
$RW_smk_fid^RANK = cRank;
In the last three lines of the calculation above we set a field on the form based on the operational percentage; if over 90% the value is “GOLD”, if over 80 “SILVER”, and so on.
Email Circulation List
When the document is set to print on submission, you can specify who to email the PDF to. This can include explicit email addresses, user IDs, and roles (defined in Workflow). You can use data from the form, so SM|CONTRACT|{job_num},{su-userid} would email site manager of the site audited and the person who perform the audit.
The completion calculation can also add to the circulation list by assigning a character variable smf_compcirc.
Alternative Update Function
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 the KCO form we have created a page KCO001 to lay out the form.
Alternative Update Function Example
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.
Fields on Alternative Update Form
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 4th 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.
Generated Form Label and Column Spans
When using the generated form these fields allow you to control the distribution of the page in Coins ERP+ (for example, to have wider labels and narrower input columns). The numbers in the two fields should add up to 8, to match the column spans used in the header.