I’m creating a survey on business criticality of applications. Logic in the meta model that if an application is deemed mission critical, then a set of additional questions pops up (=conditional questions). I’ve tried to replicate this in the survey, but it’s not possible. The workaround I’ve found is to create a new section in the survey with non-mandatory fields with a textual prompt to only fill it in for mission critical apps.
Am I correct in my assumption it’s not possible to configure conditional fields as I need?
I’ve added those fields to the survey but I can see a lock next to it, i.e. cannot enter this data. What might be the reasons and how to overcome it?
Page 1 / 1
Hello natalia,
About 1.
There is a somewhat easy way to work around this.
Conditionality on Survey questions can’t work with fact sheet fields (to my knowledge), so you can add a multiple choice question
Here you can ask about the Application’s criticality.
You can then add a Question group containing the question you want to ask when the Application is mission critical (and there you can add the fields from your meta model), you will need to manage conditionality on the Question group (top right of the question group box) and add the answer (Critical) for which the Questions in the question group will appear manually.
So the only problem with this is that you will have to manually input the criticality for your applications (or have the “same” question twice in your survey) which honestly is not that bad since you can export your answers in an excel and the IDs for your applications along with their names are there, so it’s almost ready to be imported.
About 2.
The lock simply means that the conditionality you have set in your Meta Model is not met in that case.
For example if you have a Cloud Provider field appearing only when the Hosting type is PaaS or IaaS then if the Application in scope is on premise the field will appear locked.
In that scenario the one who answers the survey will have to submit a response that changes the Hosting type to PaaS or IaaS (or update the field) and then retake the survey completing the now unlocked field since the criteria are met.
In these cases I prefer to just make it a text or multiple choice question and then just import the data (to avoid confusion from the owners/stakeholders).
Hope this helped.
Hello natalia,
About 1.
There is a somewhat easy way to work around this.
Conditionality on Survey questions can’t work with fact sheet fields (to my knowledge), so you can add a multiple choice question
Here you can ask about the Application’s criticality.
You can then add a Question group containing the question you want to ask when the Application is mission critical (and there you can add the fields from your meta model), you will need to manage conditionality on the Question group (top right of the question group box) and add the answer (Critical) for which the Questions in the question group will appear manually.
So the only problem with this is that you will have to manually input the criticality for your applications (or have the “same” question twice in your survey) which honestly is not that bad since you can export your answers in an excel and the IDs for your applications along with their names are there, so it’s almost ready to be imported.
About 2.
The lock simply means that the conditionality you have set in your Meta Model is not met in that case.
For example if you have a Cloud Provider field appearing only when the Hosting type is PaaS or IaaS then if the Application in scope is on premise the field will appear locked.
In that scenario the one who answers the survey will have to submit a response that changes the Hosting type to PaaS or IaaS (or update the field) and then retake the survey completing the now unlocked field since the criteria are met.
In these cases I prefer to just make it a text or multiple choice question and then just import the data (to avoid confusion from the owners/stakeholders).
Hope this helped.
Thank you! That clarifies the lock button - however, it’s not very straightforward then, because people will be selecting whether application is business critical or not during the survey, meaning the result will not yet be saved. And this is why the additional fields for mission critical apps will always be locked…
Personally I would do what I described in option 1 and after the survey ended I would make the fields conditional
