This article shows you how to add conditional logic to a Convert Flow, so a field only appears when a candidate's earlier answer calls for it. It's for admins and power users who build and maintain Convert Flows.

Why use conditional logic?

Conditional logic lets one flow adapt to each candidate. Candidates only see the questions that apply to them, so the form is shorter and faster to finish. You also maintain fewer flows, because one flow can cover cases you would otherwise split across several.

Here's a common example. You ask candidates whether they speak French. Candidates who answer No see your area of interest question in English. Candidates who answer Yes see it in French instead. One flow handles both audiences, and each candidate sees a version they can read.

You can use the same approach for follow-up questions that only make sense for some candidates, like asking for a referrer's name only when a candidate says they were referred.

Who can use conditional logic?

• Building rules. Super Admin, Marketing Admin, Marketing Standard and Marketing Limited users have access to Convert Flows, so they can add conditional logic. See Understanding User Roles: Compare all Roles.
• Publishing. Only Admin users can publish a flow, so an Admin needs to publish your changes before candidates see them.
• Authenticated flows. Conditional logic works on authenticated flows too. If a returning candidate's saved answer meets a rule, the conditional field shows automatically.

What can trigger a rule?

Every rule has a parent field: the earlier question whose answer decides whether your field shows. Only some field types can be a parent field.

The parent field must sit above the field it controls in the form. If you click a field and don't see a Conditional logic section, there's no field above it that can act as a parent field yet.

Any custom field or content block can be shown conditionally, except Compliance blocks.

Please note that in a multi-page flow, the parent field and the field it controls must be on the same page.

How do I add a rule?

Add the parent field to your flow first, then set the rule on the field you want to show or hide.

1. Click Convert in the left-hand navigation.
2. On the Flows Dashboard, click the name of your flow to open the Flow Builder.
3. Check that the parent field is already in the form, above the field you want to show. If it isn't, drag it in from the Fields tab.
4. Click the field you want to show conditionally. Its settings open on the right.
5. Under Conditional logic, click Add rule.
   
6. Under Show if, select the parent field. Only fields that can act as a parent field appear in this list.
7. Choose how the candidate's answer should match. The options depend on the type of parent field (see the table below this list).
   
8. Click Select the value and tick the answers that should show the field. Use Select all to tick every answer.
   
9. Under Then show the following options, choose which of this field's answers the candidate sees. Every answer is selected by default.
10. Click Add rule.
    

Please note that the comparison option and Add rule stay grayed out until you pick a parent field.

Your rule now shows as a sentence under Conditional logic, for example "Show if French Speaking is No then show Tech, Field, Business". In the form, the field is labeled Displayed conditionally, so you can spot conditional fields at a glance.

Before you publish, test the rule and make it live:

1. Click the Preview tab and try different answers in the parent field. Check that your field appears and disappears the way you expect.
2. Click Publish. Until you do, candidates keep seeing the last published version of the flow.

How do I change or remove a rule?

Editing a rule in place keeps the rest of the field as it is, so you don't need to delete the field and build it again.

1. Click the conditional field in the form.
2. Under Conditional logic, click the three-dot menu next to the rule.
3. Click Edit condition to change the rule, or Delete condition to remove it.
   
4. If you're editing, update the parent field, answers or options, then click Add rule to save your changes.
5. Preview the flow, then click Publish.

What else can I do with conditional logic?

Chain rules together. A conditional field can be the parent field for another conditional field, so you can build a path of follow-up questions.

Control several fields with one answer. More than one conditional field can use the same parent field. In the French example, one answer controls both versions of the question.

Show a question in another language. Use Customize question and Customize answers on the conditional field to write it in the candidate's language.

Add more than one rule to a field. After you save a rule, Add rule appears again so you can add another. The field shows when any one of its rules is met, so each rule works as an "or". In the example below, Area of Interest shows for a candidate who picks Tokyo or Beijing, or for a candidate who is willing to relocate.

Remove parent fields with care. If you delete a parent field, the conditional logic linked to it is removed too. Check the fields that depended on it before you publish.

What's next?

You should now be able to add, test, change and remove conditional logic in your Convert Flows. For related setup, see:

• Convert Flows - How To Create a Flow
• Creating and Editing Multi-Page Flows in Convert
• Convert Flows - Authenticated Access
• How to Create Recipes for Convert Flows, to act automatically on the answers candidates give

Questions? Contact support@beamery.com.