Dependency between fields

Dependency between fields is a feature of Involves Stage that allows an answer flow to be created in the survey form. It is used when a question field generates other questions depending on the employee's answer. This option makes the form shorter and more objective, making the fields available according to what is answered.

Let´s take a price survey form for example: after informing the price of a product, the following question could be Is this a discount price?. If the answer is no, the survey is complete. If the answer is yes, the next question can be configured with dependencies to generate more information about the discount, such as requesting a photo of the price.

Below is an example of the flow for filling out the answer fields in the App, where each field depends on the previous answer in order to be cleared.

DEPENDENCY REGISTRATION

Before you begin registering the dependency between fields, some steps must have already been completed, such as:

• Creation of the survey form;
• Creation of the questionnaire form.

Dependency can only be registered in the following question formats:

• Checkbox
• List of alternatives
• Single choice

It is possible that each answer type has a dependency flow and releases different fields within each flow. The system will execute one action at a time, however if you enter three questions in your form, the third question will only be available if the second question is enabled.

To start registration in the system, open an[ form that has already been entered into the system. In the Questionnaire tab, choose one of the fields entered and click on Options, the icon , in the right column. And right after, click on Dependency. Remember that to register a dependency when creating a form, the form must already have been saved to enable this option.

In the Field Dependencies pop-up, you have the name of the question you are editing. In Field dependent you indicate which question it will be dependent on. Remember that the list will only make the questions available in the checkbox, list of alternatives and single choice formats.

After choosing which question on the form will have the dependency, you define the validation rules. In Rule action type you choose between:

• Show/Hide: For questions that you want to show or hide depending on the answer to the previous question. In this case, the forms become more concise and objective.
• Enable/Disable: For the questions you want to display, but with the possibility of editing or not. In this case, the employee sees all possible questions, but can only edit according to their first answer.

Choose the type and then click on the Add Rule button. Include one rule at a time. In the pop-up, you will see new fields according to the answer options in the previous field.

For the field dependency a sole choice field, each answer entered becomes a value, to which an action is assigned: show/hide or enable/disable.

For checkbox fields, the answers become a value and you also assign an action: show/hide or enable/disable.

After defining the dependency actions, click the Save button on the pop-up. Also remember to save the form. You can check the dependencies you have created by clicking on the See Questionnaire option.

By system default, the form will appear replicated with the number of possible options. Dependencies are indicated with the padlock symbol, for actions marked with enable/disable.

Done! The dependencies have been configured. 

REGISTRATION EXAMPLES

In a product information form, you can have the following flow:

ENABLE/DISABLE:

Remember that if you use the enable or disable actions, the dependent question will be visible on the form from the start, but will appear disabled for editing. The moment the employee marks the option that enables the field, it will be released to be answered. This way, only one answer flow is generated.

See the example below:

Now see how it was configured:

In the example above, only one of the answers options generated an action, but each of the answers on the same form can generate a different field flow. For example, if the product is out-of-stock, you can set up another dependency flow, generating a whole number field, so that the employee informs how many products need to be replenished.

SHOW/HIDE

The show or hide actions are used to make the form shorter and more objective. In these cases, the dependent question only appears on the form when the employee selects the option that will display it.

See the example below:

Now see how it was configured: