Add option category to conditions triggers rather than duplicating for each nested option
I have a nested option in one of my forms. Basically, it's A::1, B::1, B::2, B::3, C::1, C::2, etc.
I understand that I could build conditions off A, B, C, where answering B would trigger a follow up to ask "1, 2, or 3?", but this would nullify the value of nesting the options. On the backend, it means I need to build out the same set of conditions for each option nested on the same category.
It would save time building out conditions on nested fields and reduce the margin of error to allow the category to also be listed as an condition. Something to the effect of [IF B:: THEN], rather than the same set of options three times for each of B::1, B::2, & B::3.
Thanks for the feedback about triggers. You point out an interesting idea that seems like it would be more efficient. Currently we don't have anything on the roadmap but I will document the information. We are in the process of releasing a new version of triggers this week that makes that has some performance improvements so be on the lookout for that.
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.