Property | Description |
|---|---|
Process Code | Identifier of the process (hidden) |
Activity Code | Identifier of the activity (hidden) |
Type | The type of the control: Group (groups controls together), Control (displays information), Button (for navigation, see Buttons) |
Label | Caption of the control on the mobile client. The framework supports Unicode characters in most controls. see Using emojis as button captions for demonstrations using Unicode emojis as button captions. |
New Line | Explicit new line after the control |
SubType | The specific type of the control: Label, Textbox, LiteralHTML, FileUpload, Image, Signature, CheckBox, Dropdown |
Source Type | Source of the value to display: <none>, Parameters, Field, Processes |
Source Code | Field from the activity's table, activity, or process to display. Also the parameter where user input is stored. |
Style | Apply inline styling for the controls displayed in the portal. The style wizard helps set up the most common styling options. |
Visible | Control the visibility of controls dynamically. Use the value from the source fields (table field or parameter) and a function whose return value is boolean. |
Activates Next Record | Triggers Anywhere Mobility Solutions to identify a record in the database after the user inputs data in the client, using the user input, filters, key settings, and flow table relations. |
Expression | Initial value for editable textboxes with Source Type=Parameter. Also displays values for non-editable controls like Textbox, Label, and LiteralHTML. |
Editable | Marks whether the user can interact with the control. Not applicable to all variations. |
Mandatory | Checks whether the parameter has a value. Only in combination with editable textboxes. |
Table Name | The table bound to the activity. |
Field Name | The field displayed on the mobile client. |
Line No. | Makes the control unique. |
Activates Next Record
When Activates Next Record is set to true, Anywhere Mobility Solutions tries to identify a record in the database when the control is validated, either at the start of the activity, when the expression of a non-editable parameter evaluates, or when the user submits the form after inserting data. Set this field to true when information from the record is needed in the next activity. Set it to false when the user input does not retrieve a record.
Mandatory
To prevent a user from skipping a required input field, mark an editable control as mandatory. The parameter linked to the control is always checked when the user submits the form. When no value is entered, an error returns to the user.
Expression
Use expressions on a control to display results of custom functions, show several fields on one line, and set initial values in a textbox. A good example of an initial value is the current field value of the activity record.