Unlinked Mobile UIs
Mobile UIs can be marked as "unlinked". In that case, an additional button with the description of the Mobile UI will appear if the mobile worker is on site. Clicking the button will create an additional itemsPlanned
attachment with the name of the Mobile UI as the reference code and the processFlow
. The corresponding Mobile UI will be opened to allow the mobile worker to edit the widgets defined in the Mobile UI. Once the task is signed, additional unlinked Mobile UIs can not be added anymore (unless the allowPrematureSignature
preference is set). By default, unlinked Mobile UI items may only be created once per task. When clicking on the additional button with the description of the Mobile UI, the formerly created Mobile UI entry will appear. However, when setting the allowMultipleUnlinkedItems
, the mobile worker will be asked if a new item should be created.
allowMultipleUnlinkedItems | ||||
---|---|---|---|---|
Type | Default Value | Example | Android | HTML 5 |
Boolean | false | true | + | + |
Forms
Mobile UIs may also be marked as "form", independently of the "unlinked" value. In the case of a form, the Mobile UI will remain open even after having closed the task until the form was individually confirmed by the mobile worker (Android only).
Note that the ERP system must be able to interpret this type of attachment.
Unlinked Process Flows
By default, unlinked Mobile UIs are always displayed during the on site phase. The related icon can be surpressed by specifying a list of comma-separated process flows in the processFlows
field for which the unlinked Mobile UI should be shown. If the process flow of the task does not match with one of the process flows in the list, the Mobile UI will not be displayed.