Open miabonardi opened 11 months ago
Using separate .YML's for each "form" might be a good option? I'm unsure how these interactions work and if the "master interview" would be able to pull all the gathered info from the questions asked so far.
But I think if we If we can break them into separate files, and keep all the info gathered available to auto-populate from, I think it would allow complete control of questions order and not risk asking for the same piece of info twice.
Using separate .YML's for each "form" might be a good option? I'm unsure how these interactions work and if the "master interview" would be able to pull all the gathered info from the questions asked so far.
But I think if we If we can break them into separate files, and keep all the info gathered available to auto-populate from, I think it would allow complete control of questions order and not risk asking for the same piece of info twice.
Absolutely! We use the method of a main.yml
for the main order that refers to sub interview orders in the individual yml files for each form for several other projects. We also add a shared.yml
for any custom questions (not AL) shared by all forms.
See: