Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

offer a way for apps to enforce conditional logic on question presentation #369

Open
eric-jahn opened this issue Sep 19, 2020 · 1 comment

Comments

@eric-jahn
Copy link
Member

Missing in our survey question schema is a concept of parent child questions. For example we need to ask a set of questions if the disabling conditions is true and another set of questions if its false. Currently, we don't have that feature in HSLynk

There would have to be validation performed on a previous response, which may not have been submitted to HSLynk yet. So maybe questions could contain validation requirement metadata, which gives guidance to the app, as to when/if it should display the question to the user.

@eric-jahn
Copy link
Member Author

eric-jahn commented Nov 13, 2020

from @suryayadavalli "efficient design for this would be sending the user's response back to the cloud and then determining the next question accordingly. We need not consider this as a submission but the reason to send the response back to the cloud is to route the user to the subsequent question based on his response.
Coming to the design and implementation I feel that we should consider few scenarios where the choices for the current questions are multi select check boxes, single selects and also few user entered responses. (for example, you might want to redirect the user to.question 10 if the age of the person is above 59 and question 20 if the age of the person is less than 59 - I am just giving a hypothetical example. Also, another scenario is, what if you want to route the user to the next question based previous 2 responses, (not just 1)
Also, do we know if we just handle this at question level but also sections. For example, if the user don't have children, you might want to skip entire section and move on to a different section."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant