What are the Counter Widget Properties
A counter can keep a tally of any item or object. It comes along with ‘+’ ‘-’ and ‘reset’ buttons, which makes counting easy on forms. You can either add, subtract or reset the counter button while filling the workflow. For example, if you have multiple objects to inspected while collecting data, all you have to do is, keep on clicking ‘+’ each time you come across a new object. To add ‘Counter’ to your workflow, drag it from the left panel and drop it to the digital mobile screen in the middle.
By using Unit property, you can mention the unit that you want to have in your counter. It could be anything. For example, it can be ‘Defects’ found out during an inspection process
You can change the name of the ‘Counter’ using a label property. It is ‘Counter’ by default. On the right panel, go to the label section and you can type the required text that you want. The same name will appear on the workflow. For example, you can keep the label of your Counter as ‘No. of fire extinguishers in the area.’
You can use this property to make that ‘Counter’ mandatory to be filled. Some fields in your workflow might be mandatory, while some might not be.
For example, ‘Counter’ field can be set to ‘Yes’ in the required property when you want to make the field mandatory. So, while filling out a workflow, the user will have to compulsorily add the counter while filling the mobile workflow, without which the workflow wouldn’t be submitted.
Every field will have a unique identifier. No two unique identifiers for fields will be the same. Please note that ‘Unique Identifier’ property is just for reference purpose only. The user need not have to do anything to this property. It can be referred when there are fields created with the same names. When you create two fields with the same names, it might get confusing when you are setting a condition and you wouldn’t know which field is which.
For example—if you have created a field ‘address’ – and set a visibility condition to it saying the ‘address’ field will be only visible if you have entered the ‘Phone number.’ But if there are two fields that say ‘Phone Number’ – it will be difficult to set a visibility condition since both the fields have the same name. Both of these fields ‘Phone Number’ will have different unique identifiers. You can check the unique identifier and then set the condition accordingly.
Visibility Condition in the property for the ‘Counter’ is used to specify a condition. If you apply any visibility condition, it implies that the ‘Counter’ field will only be visible if it satisfies the condition that you have set. Visibility condition can be set by specifying the condition – you can do that by clicking ‘condition not specified.’
For example—you might create a Field ‘Fire Extinguisher Count’ which will be only visible if the user chooses ‘Yes’ option in the previous choice list ‘Are there fire extinguishers in the premises?’ Visibility conditions can help you control the type of input during the filling of a workflow by the user.
Validity Condition in the property for the ‘Counter’ is used to specify a condition. If you set any validity condition, it implies that the ‘Counter’ will only be valid if it satisfies the condition that you have set. Validity condition can be set by specifying the condition – you can do that by clicking ‘condition not specified.’
For example—you might create a field ‘Gas Meters’ which will be only valid if the user enters ‘Yes’ in the earlier field ‘Are there gas meters?’ Otherwise, it would be invalid and show an error message. Validations can help you control the type of input during the filling of a workflow by the user. You can also customize an error message that you want to display by typing the message in ‘Validity Error Message.’ This message will be displayed when the validity condition does not match with the given input.
The error message could be “This counter is only for gas meters.