Me again.. I’m having some trouble with creating the Workflow for this ‘checklist’ style element, with a Yes/No function. I’ve read around the forum and seen that Custom States are needed?
The workflow refers to 1 data type only, so it’s quite linear. Any help would be much appreciated!
Additionally, this doesn’t have to be a yes/no, it could just be a ‘Yes’ checkbox if that’s easier for the workflow as I need to do about 30+ of these.
Custom states are not necessarily needed (depends on what you want to do), but you may want to change the checkbox into radio buttons instead? Since now, users can technically check both yes and no.
With radio buttons you’ll be able to get a yes/no value from a single element.
Hmm, actually, sorry I was a bit quick here, this unnecessarily complicates things. The easiest solution is probably to drop the “no” altogether and just include one regular checkbox with the label “Yes”, and then use the Checkbox is checked state (which returns a yes/no).
If you’re fine with that UI change, then this is the simplest setup.
Simply save the response to that relevant input I.e., have they introduced us to other stakeholders? Yes.
Furthermore, this ‘Yes’ will be used in a scoring system in the future. I.e., Each Yes = 5% which contributes to the total score of the account. If that makes sense and whether that changes things?
If each cell of the repeating group contains a data type where you want to save the “Yes”, then you can use auto-binding to automatically write in the database whenever the value changes.
Because of scoring needs, and likelihood of dynamic number of questions in different forms, and so perhaps a different percentage value applied to each ‘yes’ response on different forms, you may want to just use a custom state as a counter when they check a checkbox value to yes. Then when scoring take custom state count divided by total question count and have simple score if each yes is of equal weight.
But I suggest this only because I would anticipate dynamic needs for different forms, but in your app the form may be static.
Hi @boston85719 , thanks for the response here. The score weighting will be the same on every question. Let’s say 5% as an example to keep things simple. Will this make the process easier without needing custom states?
Is the form static or dynamic, which for me is, will there only ever be one form with an unchanging number of questions or would either the app have multiple forms of different lengths or perhaps the single form could have questions added or removed?