What are the Barcode Widget Properties

Barcode Widget

Barcode widget can be added to your workflow for allowing data capture through scanning of the barcode. When you scan a particular barcode, the information relating to that product/object can be fetched easily – without having to fill those details. To add Barcode to your workflow, just drag the widget from the left panel to the digital mobile screen in the middle.

Barcode Widget—Properties

Text Editable

The property allows the app user to edit the barcode value with free text while filling the workflow.

Widget Layout

Widget Layout default value is Two Line. Use the Widget Layout property to set to name (label) and value to a single line or two lines. Example—Two Line layout displays the widget name (label) on one line and the value (to be filled in) on a second line. One Line layout displays the widget name (label) and the value to be filled in on a single line. 

On the left panel, if you can see ‘Advanced’ option besides ‘Widgets.’ Advanced stands for advanced widgets that you can use in your workflow. Just as the basic widgets, you can drag these widgets and drop those on the digital mobile screen in the middle. All of the widgets will have some properties, which are explained here.

Two Line

One Line

 

Scan QR Codes?

Allow the app user to also scan QR codes along with the bar codes in the scanner widget.

Device Profiles

The barcode widget supports the built-in camera as well as the external barcode reader devices to scan a code. To enable an external device support, the device’s configuration needs to be added to the widget properties while designing the workflow.

Default Device Profile

If multiple barcode readers are available and configured in the device profiles, one of the profiles need to be set as the default, which gets automatically activated when this widget is visited while filling the workflow on a mobile device.

Label

You can change the name of the ‘Barcode’ using a label. It is ‘Barcode’ 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 might create a field ‘Machine Barcode’ to scan a particular code on the machine.

Required

You can use this property to make ‘Barcode’ mandatory to be filled. Some fields in your workflow might be mandatory, while some might not be. For example, ‘Barcode’ 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 choose to fill the Barcode field, without which the workflow will not be submitted.

Unique

This property indicates if only unique values are to be accepted by the user for this field. While submitting the workflow having a unique field, if any previous submission exists with the same value for the unique field, the data submission is prevented with an error displayed to the user saying that the value for the set unique field already exists.

The duplicate values can be updated by the user after getting the error on the mobile device, and the record can be resubmitted with a new value.

Unique Identifier

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 Conditions

Visibility Condition in the property for the ‘Barcode’ is used to specify a condition. If you apply any visibility condition, it implies that the ‘Barcode’ 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 ‘Machine A Barcode Scan’ which will be only visible if the user chooses ‘Yes’ option in the earlier choice list ‘Is there a Machine A?”

Validity conditions

Validity Condition in the property for the ‘Barcode’ is used to specify a condition. If you set any validity condition, it implies that the ‘Barcode’ 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 Barcode ‘Machine Barcode’ which will be only valid if the user chooses ‘Machine’ in the earlier choice list from the workflow. 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 is only for Machine Barcode.”