The NFC tool (compatible with Android devices only) allows the collection of Near Field Communication (NFC) tag values via a mobile form. The tool also provides the ability to parse the returned code into multiple data fields and assign them as "destination" fields to other fields in the form.
To scan an NFC tag from within a form, the user taps the "Scan" button and then holds the Android device near the NFC tag. The device's internal NFC tag reader reads the tag and transfers the tag's data sequence to the NFC field.
Check out the Data Lookup help topic for more info on parsing and destination fields.
Caption text: The caption is used in most cases to ask the question. In others it may be a column heading. This is a required field. Please keep in mind that captions will wrap when form elements do not fit within the width of the screen. It is important to consider how your captions will be displayed. Captions on a larger screen might look perfect, but on a smaller device, they may be forced to wrap several times. In this situation, a smaller caption should be used.
Hint: Provides additional information to the mobile form user on how a question (i.e., Caption text) should be answered. The Hint font size is smaller than the Caption font size.
Additional HTML styling can be applied on hints and captions.
Data name: Because this is a required field, doForms will default the Data name to match the Caption or Label. If these are blank, doForms will generate a generic Data name name with a sequential number (such as "untitled10"). Since it is used throughout the system, it is recommended that you enter a descriptive Data name that is easily identifiable. Nondescript Data names are difficult to find and select at a later time (e.g., when performing a calculation).
Default Value: The value of the field first presented to the user when they see the question. Unless the question is marked as Read Only, the mobile user will be able to change the value. This is very useful where the answer to a question is likely to repeat itself over and over. Setting a default value minimizes the work for mobile users. Note that repeating values can also be set on the mobile app using the Remember Answer option.
Button Type: These options decide whether a "Read" button is displayed or an NFC icon is dispalyed when going to read an NFC tag.
Allow Edit- this setting allows the user to re-read an NFC tag if necessary. If this setting is unchecked once the user scans the first tag the field will become read only and they will not be able to re-scan.
Allow Manual Entry- when using the NFC tool users have the ability to click the scan button or to type in a NFC value manually. If this setting is unchecked the user will only be able to scan a tag they will not be able to manually enter anything into the field.
Parse: Select the Parse checkbox to parse the returned tag into multiple data fields and assign them as other fields within the form. When this checkbox is selected, the following options for Delimiters and Destination fields will appear:
- Delimiter fields: Enter Start, Separation, and/or End Delimiter values (delimiters are used to specify the boundaries between separate regions in a scanned data string). If entering delimiters, note that the Separation Delimiter field is required, but the Start Delimiter and End Delimiter fields are optional.
- Destination fields: Select one or more existing fields that will receive the parsed NFC tag value(s). The first parsed value will go into the first Destination field. Continue adding additional Destination fields, and selecting existing fields for all parsed values. Note that the number of destination fields must be equal to or less than the number of parsed values.
- Action button only: This setting allows the user to use an action button instead of a text box field with a scan icon or button. This setting also allows the user to read the NFC tag and have the action button dissapear once read if the allow edit option is unchecked. When not using this setting the NFC field, once read, will display the full text of the NFC tag in a single field. This setting allows the user to hide that field and only show the data parsed into individual fields.
Length: If desired, select the Length checkbox and enter values in the Minimum and Maximum fields that appear when select this setting. These values act to validate the character length of the barcode input in terms of a minimum and a maximum number of permitted characters (note that spaces are counted).
Appearance: doForms allows you to set a default set of appearance parameters. This eliminates the need for you to have to set colors and other parameters each time you add an element to your form. You can however override the default settings for any tool by simply picking the Custom option. You can also edit the default by clicking on the edit defaults option.
See Appearance Settings
Justification: Allows you to apply text justification settings to certain elements of the tool. Choose the appropriate radio button for the Caption, Hint, and/or Answer fields as follows:
L: Left-justifies the text.
C: Center-justifies the text.
R: Right-justifies the text.
Remove Space: This parameter is used to remove the space just before and just after the tool. By removing space two elements can be made to appear linked or as a single element.
Read only: These settings allow you to control which users can enter data into or edit this field. The settings are as follows:
- View data edit: Restricts a web portal user from editing this field when editing a submitted form through the 'View data' tab
- View data new: Restricts a web portal user from entering data into this field when filling out a new form through the 'View data' tab.
- Dispatch edit: Restricts a web portal user from editing this field when editing a submitted form through the 'Dispatch' tab.
- Dispatch new: Restricts a web portal user from entering data into this field when filling out a new dispatch through the 'Dispatch' tab.
- Mobile: Restricts a mobile user from entering data into this field when filling out a form.
- Web App: Restricts a web app user from entering data into this field when filling out a form.
- Form Links: Restricts a web portal user from editing this field when editing a form that was sent using a form link
Required: These settings allow you to control which users are required to enter data into this field. The settings are as follows:
- View data edit: Requires a web portal user to enter data into this field if editing and saving a submitted form through the 'View data' tab
- View data new: Requires a web portal user to enter data into this field when filling out a new form through the 'View data' tab.
- Dispatch edit: Requires a web portal user to enter data into this field if editing and saving a submitted form through the 'Dispatch' tab.
- Dispatch new: Requires a web portal user to enter data into this field when filling out a new dispatch through the 'Dispatch' tab.
- Mobile: Requires a mobile user to enter data into this field when filling out a form.
- Web App: Requires a web app user to enter data into this field when filling out a form.
- Form Links: Restricts a user from submitting a form link without answering this this field.
Only display this question if
This is a very powerful option as it allows you to hide form elements, only exposing them if the answer to a question in your form meets the criteria you have set. Being able to hide fields unless they are needed makes form more user friendly. For example, if you have a Choose One question with the answers Yes and No, then you can say "Only display this form element if" the answer to the Choose One is "equal" to "Yes." You can combine criteria with other criteria, thus creating complex criteria for showing/hiding form elements.
This option allows you to navigate the user to a specific location in the form based on how they answer the current question.