Conditional Questions allow you to upload Standardized Information Gathering (or SIG) questionnaires into your Loopio Projects, making it possible to show or hide Questions based on dependencies.
Note: Loopio supports Conditional Questions in SIG questionnaire versions 2019 or newer.
Permissions Required: Loopio-wide Projects Access, Level 2 (Creator) permissions or higher required to create Projects. Learn more: Platform-wide versus Project permissions
In this article:
- How do I Import Questions in a SIG File into my Loopio Project?
- Saving the Source File as .XLSX
- All Questions Will show in the Import Screen
- New Indicators and Warnings
- Compliance Answers will be Automatically Detected
- Responding to SIG Questionnaires in Loopio
- Exporting a Completed SIG Project
- Can I Use SIG Questionnaires to Create Project Templates?
For an overview of SIG Questionnaires in Loopio, take a look at this video:
How Do I Import Questions in a SIG Questionnaire Into My Loopio Project?
The process of Importing a SIG file is very similar to the current workflow to Import an Excel file into Loopio. However, there are a few things to note:
The Source File Must Be an Excel Workbook (.XLSX):
SIG questionnaires are normally issued as Macro Enabled files (or .xlsm), which are not compatible with Loopio. However, you can re-save your files as Excel Workbook files (.xlsx) to easily take advantage of Conditional Questions in Loopio. The resulting file will still have the logic found in the original SIG questionnaire, allowing Loopio to recreate that experience in your Project workspace.
The Import Screen Will Show Every Question Even if They Are Hidden in the Source File:
Every row in the SIG questionnaire will be shown in the Import window and all Questions will be visible. This is to ensure that all Questions are properly captured:
Note: Only the parent questions will be shown after the Import process is complete:
Indicators and Warning Messages Will Appear on the Import Screen:
You’ll notice a couple of new indicators on the left side of the Import screen to differentiate both types of Questions:
- A filled gray diamond for parent Questions
- A hollow gray diamond for child Questions
Note: Some Questions might even have both types of diamonds to show that it is a parent Question that’s dependent on another parent Question:
On the other hand, warning messages will appear in the form of a yellow triangle if a User tries to Import child Questions without selecting their respective parent Question:
Note: These warning messages will clearly indicate which Question(s) need to be imported to remove the warning:
Compliance Answers Will Be Automatically Detected
As with any other Excel document that has drop-downs, the compliance answers will be automatically detected for all Questions (parent or child).
Responding to SIG Questionnaires in Loopio:
You'll be able to follow the current process to respond to Projects in Loopio. However, given this is a SIG Project, only parent Questions are visible by default in the Project List View, and child Questions will appear right below their respective parent Questions exclusively after the User responds to them by selecting Yes in their Response drop-down. A green banner across the top of the page will indicate how many new follow-up questions have been added to the Projects.
When the User selects Yes in the Response drop-down to a parent question while in Focus View, the Next Question text will be updated to show the first child Question.
Source View works similarly to how you would imagine the Excel sheet. When the user selects Yes in the Response drop-down to a parent Question, additional Questions will appear. A green banner across the top of the page will indicate how many new Questions have been added to the Projects and additional Questions will appear from those hidden rows.
Note: For all Views, child questions will be hidden if another selection is made on the Response drop-down, as only responses of Yes show more Questions in a SIG questionnaire.
How Does Magic Run on SIG Projects?
Magic will run on all Questions (even the ones that are hidden). Child questions will remain hidden even if Magic finds a response but the parent question was either not filled in, or the compliance answer was not filled in with Yes.
Looking at the top of the Project workspace, the Question count pills and the progress bar will be updated if there are new questions that appear (or become hidden) based on the user's actions.
Assignees and Reviewers carry down to all child questions, so if an unanswered parent question is assigned to a user, the child questions will also automatically be assigned to that user. This is to ensure that the user can access and see the child questions (especially important if the assignee only has assignee permissions in the Project).
Aside from this, all other assignment workflows remain the same.
Note: If that user is not the correct person to answer the child questions, they may need to prompt the Project Owner to reassign those questions.
Exporting a Completed SIG Project:
You’ll be able to Export your completed Project to all available options and only the visible Questions will appear in the exported file.
It’s important to remember that if you choose to Export to the source document the macro in the original file will no longer be there, which means that child Questions will not show or hide if you decide to change your responses to parent Questions in the exported file. However, upon Export, all the rows that are visible in your Loopio Project will be shown, and any hidden Questions will remain hidden.
Note: it is very important to review the Export screen, as there are helpful warning messages that will show up if answers are missing. This encourages the user to not have any unexpected blank child questions in the exported file:
Can I Use SIG Questionnaires to Create Project Templates?
The ability to work with SIG questionnaires is also available for customers to leverage in Project Templates.
This functionality could be helpful for teams who proactively send out SIG questionnaires as part of their security package.
The Workflow would look like this:
- Create a Project Template
- Import a SIG .xslx file through the source document Import
- Run Magic
- Publish a draft
- Create a Project from the Project Template