Mode
The Mode node adds a switcher element that allows the user to report the start and the end of a certain process or action, for example, start/end of the working day.
When the Mode node is loaded, it is set to one of the states ("A" or "B", depending on the settings). When tapped, it switches to the other state. If the transaction checkbox is ticked, a transaction for state "A" is sent to the server reporting a command event matching the mode "A" ID.
| Option | Description |
|---|---|
| Node (A) ID |
The identifier for the Node in state "A". This value is shown in the transaction after the user switches the node from state “A”to state “B”. |
| Node (A) label |
The label for the node in state “A”. This value is shown on the client when the node is in state “A”. |
| Run Context | Context to run when the user switches the mode. If the value "0", no context is run. |
| Remember | Saves the state persistently for the user. Logging out or exiting the
application doesn't clear the last state of the node. If the Mode node is included in several menus, states of multiple Mode nodes with the same ID are linked. |
| Confirmation |
Show a confirmation window asking for the user’s permission to send the transaction. |
| Transaction |
Send transaction with the node ID to the server when the user switches the mode. |
| Require scanning | Require the user to scan a tag or a code (depending on the app type) when switching the mode. |
| Scan Behaviour |
Deprecated field. |
| Report Active time | Include the time between mode switches in the checkout transaction. |
| Remember only last location | Require the user to scan the same tag again when switching the mode. If the user reads some other tag, the mode isn't switched. |
| Data Info | Information for the user shown next to the node label. |