The toggle field can also be a multi-select Lookup field. In that case, the selections the user makes on the primary form will display as many branch logic forms as you have defined for those selections.
Branch Logic forms contain elements like other forms (fields, instructions, blocks, etc.). You can display as much additional information as you want inside the parent form. You create and edit branch logic forms in the same way you work with intake, auxiliary, and other forms, on the process management page (Admin > Processes, Forms, and Profiles).
Branch Logic Block on Branch Logic Forms
You can place a Branch Logic block on a branch logic form (for a form within a form within a form), but will need to guard against a circular setup - a form that branches to another form, but that form branches back to the first branch form, etc.
You might want to ask applicants if their primary language is English. If the response is Yes, you want the form to display the standard Language dropdown with English pre-selected. But if the response is No, you want the form to display the standard Language dropdown (with no language pre-selected), and also ask additional questions like what the applicant's primary language is, their level of proficiency in English, and so on. To accomplish this, you would:
Create a field for the initial Yes/No question "Primary Language is English" (if one doesn't already exist).
Create a branch logic form for the Yes response on the Admin > Processes, Forms, and Profiles. Add the Language field to this form and set the default value as English.
Create a branch logic form for the No response. Add the Language field to this form, as well as any additional fields, instructions, and blocks necessary to collect any additional information.
Add the Branch Logic block as an element on your primary form (in this example, probably an Intake form). Expand the Branch Logic block and set the options: select your Yes/No field for Toggle Field, and the appropriate branch logic forms for the Yes and No responses.
Note how you need to build in reverse: create/decide on a toggle field, build the branch logic forms, then place the Branch Logic block on the parent form (after you have the pieces the block needs).
Branch Logic based on Existing Information
Although branch logic is often used during intake to make different forms appear based on a user's selection, it can also be used for fields that already have a selection made, whether earlier in an intake or after a case is accepted.
For example, a site could have an auxiliary process called "Additional Questions" that appears on open cases. The form called by that process would contain a branch logic block with a toggle field for a value that has already been entered (legal problem code, funding code, county of residence, a custom field, etc.) As soon as a user clicks the "Additional Questions" link, the branch logic block would display the appropriate questions (the branch logic form configured for that legal problem code, funding code, etc.). If a site has several sets of questions based on a single field, one link could replace several separate links.
The Hidden option could also be used so that the user could not, on that form, accidentally change the toggle field value.
Branch Logic Form Toggle Button
This block is useful in "Show/Hide" situations to display, or not, a branch logic form. It allows you to avoid creating an unnecessary Yes/No toggle field for the 'full' Branch Logic block.
In the example, an agency wants to display a branch logic form if an applicant has previous applications, but has no need to create a "Previous Applications" field and store a Yes or No value for it.
