Process Level Question Branching allows branched questions to be shared between forms in Grant Lifecycle Manager (GLM) and Scholarship Lifecycle Manager (SLM), creating a more seamless experience for applicants moving through a process. The feature hides a group of questions using conditional logic until an applicant answers a triggering question. That branched logic can then be shared across forms so that the trigger question and its corresponding branched groups are connected between forms. When an applicant submits the first form, their response to the trigger question carries forward to the next form, defaulting to the same answer and displaying the corresponding branched question group automatically.
User Role: Administrator
When to Use Process Level Question Branching:
- An application form uses branching logic and the same trigger question and branched groups need to carry over to a follow up form.
- Applicant responses on one form should pre-populate and drive conditional questions on other forms without requiring the applicant to re-enter the same information.
This feature is available with the Standard license and above. Contact Support with any questions about your license or to enable this feature in your site.
The Process Level Question Branching feature allows you to share branched questions between forms making the application process easier for your applicants.
Configure Process Level Question Branching
To configure the process level question branching, add a trigger question with branching logic on one form, then share that question onto another form in the same process.
Add a Trigger Question and Branched Groups
To add a trigger question and configure branched question groups on a form:
- Click Tools on the upper navigation bar, then click Process Manager.
- Click the process name.
- Click the process stage.
- Click the pencil icon.
- Click Standard.
- Select the question type.
- Configure the question, then click Save Question.
- Click Add Group.
- Enter the group name, click the Show this Group based on Question Branching Rules checkbox, then click Save Group.
- Click the pencil icon to edit the group.
- Click Add AND Rule or Add AND/OR Rule Group depending on your needs.
- Configure the rule group, then click Add Rule.
- Click Save Group.
- Click Standard to add questions to the branched group, then configure each question.
Repeat steps 8 through 14 for each additional branched group needed.
Share the Trigger Question onto Another Form
To share the trigger question from one form to another in the same process:
- Click the pencil icon on the form the question will be shared to.
- Click Add Group.
- Enter the group name, click the Show this Group based on Question Branching Rules checkbox, then click Save Group.
- Click the pencil icon.
- Click Add AND Rule or Add AND/OR Rule Group depending on your needs.
- Configure the rule group, then click Add Rule.
- Click Save Group.
- Click Shared.
- Select the radio button for the trigger question from the originating form, then click Add Selected Question.
Test Process Level Question Branching
It is recommended to proxy in as an applicant to confirm the branching is working correctly after configuration.
Test the Trigger Question
To test the branching logic on the trigger question:
- Proxy in as a test applicant.
- Click Apply.
- Click Apply on the process.
- Fill out the form and test different options on the trigger question to confirm the correct branched groups display based on the selected criteria. Select the response to be used for testing, then Submit.
Stop proxying as the applicant and move the form through the next stages.
Test the Shared Question
To confirm the branching carries forward to the next form:
- Proxy in as a test applicant.
- On the Applicant Dashboard, click the assigned form to start.
- Confirm the trigger question defaults to the same response selected on the previous form and the corresponding branched question group displays correctly.
If the form displays the correct defaulted response and branched group, process level question branching is configured correctly.