Request/Dropzone Form Builder

Created August 23, 2022
Updated May 23, 2025

Request vs Dropzone

Both Request and Dropzone feature enable users to collect data from others, but they serve different purposes**.** The primary difference between Request and Dropzone is the scope of your target audience.

• Request is typically used for one-on-one communication or for a small and specific group of recipients. It is ideal for situations where you need to collect information from a selected few.

• On the other hand, Dropzone is designed for broader, more open data collection. It allows you to gather information from a larger and possibly unknown number of people. This makes Dropzone more suitable for collecting data from a wider range of audience.

Form Builder Options

In both the Request and Dropzone module, Sypher provides two options for creating a form:

1. Select Template – This option allows you to reuse your previously created templates or choose from a variety of pre-made templates.

2. Start from Scratch – This option enables you to build a custom form using Sypher’s amazing features.

Below detailed information is designed for users who want to start from scratch. If you prefer to use a template, please proceed to the Templates section.

Rule Builder

For both Request and Dropzone, the Rule Builder allows you to set logical conditions, create various branches and pathways for different recipients, and dynamically control the flow of your forms. This feature includes three components: “Effects,” “Add Condition/Group,” and “Fail when undefined.”

1. Effects

Sypher provides 5 different effects for you to choose from:

1. JUMP_TO: This feature allows recipients to skip to different questions within the form.

2. HIDE: This feature hides your selected element when a recipient meets a specific condition that you have set.

3. SHOW: This feature works opposite of HIDE and displays your selected element when a recipient meets a specific condition you have set.

   Important: The selected element will not be hidden when others first load the form; it will only be hidden when recipients interact with the form. To hide your element as soon as the form opens, select the “Fail when Undefined” option.

4. ENABLE: This feature makes your selected element interactable to the recipient when they meet your specific condition.

   Important: The selected element will not be disabled when others first load the form, meaning they could input one character before the condition is checked and the element becomes unresponsive. To disable your element immediately when the form opens, select the “Fail when Undefined” option.

5. DISABLE: This feature works opposite of ENABLE and makes your selected element un-interactable or unresponsive to the recipient when they meet your specific conditions.

2. Add Condition and Group

Linking logic, conditions, and groups to your effects.

This feature allows you to create an “OR” or “AND” logic, enabling you to narrow or expand your conditions for the target audience. For instance, as shown in the image below, you can hide a specific element if the recipient’s email contains “123” OR “456.”

Next, you can click the “Add Condition” button to add a conditional “if” statement, then configure your condition. From there, you can choose the element in your form, select the relationship (such as “equals to,” “start with”, and more), and enter the compared value.

Finally, you can click the “Add Group” button to create a group structure for your conditions. Within this group, you can add multiple conditions using the “Add Condition” button. This helps you organize your conditions based on your target audience and allows advanced conditional logic.

3. Fail when Undefined?

At the bottom of the Rule Builder page, you can select the “Fail when Undefined” option. This feature makes sure that the form runs all the conditions and preloads the SHOW and ENABLE effects as soon as the form is open. This setting is often useful for these specific effects:

• SHOW: To make an element visible when a recipient meets a condition, it must be hidden initially.
• ENABLE: To make an element responsive or enabled when a recipient meets a condition, it must be unresponsive or disabled first.

If this option is not enabled, the form will still show and/or enable elements, but the conditions and effects will only be applied once the user interacts with the form.