NFC

Follow

A NFC widget - available for paid accounts only - allows the collection of Near Field Computing (NFC) tag values. Note that the type of tags supported is a function of the NFC sensor in the mobile device hardware (if any).

This widget also provides the ability to “parse” the returned code into multiple data fields and assign them as “destination” fields to other widgets.  In the example below, an automotive code is being parsed into make, model and year components and a value is assigned to each corresponding answer fields.

When displayed on the mobile device, the NFC question widget will look similar to the following:

Adding the NFC widget is as simple as using a “drag and drop” motion to place on the form canvas. 

The NFC question widget includes the following special properties that you can use to control the look and behavior of NFC:

Caption text - Refers to the question caption as presented to the user. Think of this as the title for the question; it should be self-descriptive. We recommend no more than three words for optimal display on mobile devices.

Hint - Additional help for the question will be displayed; short clear sentences work best. Use 80 characters or less for optimal display on mobile devices. The maximum number of characters is 500, including spaces. The following HTML formatting tags are currently recognized:

Android: <br>, <i>, <b>, <u>, <font color="xxx">, <H1>, <H2>, <H3>, <H4>, <H5>, <P>, <a>, <div>;
iOS: <br>;
PDF reports: <br>, <font color="xxx">.

Data name - Represents the name of the data that will be displayed in column headings. This property is automatically filled in based on the Caption Text, but may be modified in the properties area. We recommend one or two word data names to keep column headings short. The maximum number of characters is 30. Spaces are not permitted in the Data Name field. 

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.

Read only - Determines whether or not this field can be edited. This is used in combination with a Default Value.

Required - Determines whether or not this field must be filled-in before continuing to the next question. On the mobile device, a form with an empty required field may be saved as “incomplete” but not as “complete” and hence cannot be sent to your website.

Length – Validates the character length of the user input in terms of a minimum and a maximum number of permitted characters (spaces are counted).

Parse – Use this option to “parse” the returned code into multiple data fields and assign them as “destination” fields to other widgets.  A “separation delimiter” value is required, but the “start delimiter” and “end delimiter” are optional.

Destination fields – These are the question widgets in the form that will receive the parsed code values.  The first parsed value will go into the first destination field.  The second parsed value will go into the second destination field, etc.  The number of destination fields must be equal to or less than the number of parsed values.

Advanced - Clicking on the Advanced arrow will reveal “Relevance conditions” and “Skip conditions” properties that can be used of further control the behavior of your form using sophisticated logical statements. Please refer to http://support.doforms.com/hc/en-us/articles/200446034-Using-Relevance-Skip-Logic for more information on these properties. 

Have more questions? Submit a request

Comments

Powered by Zendesk