Condtional Requirement logic not working as expected
Thursday, October 19, 2023 at 03:31pmI'm working on a document where the signer is answering Yes/No questions, which I have set up as Radio fields (with radio groups) as Yes No options. We have different sections, where if the signer chooses a single Yes option, they need to fill in a text field to provide additional notes.
What I'm trying to achieve is if a signer chooses a single "yes" option for questions in a particular section of the document, then they need to fill out an additional notes field for that section; independent of how they answered the other questions in that section. There is a single additional notes field where they are supposed to provide notes for the questions in the section.
What I've done is set up conditional logic on each "Yes" radio option, where if it's selected, then require the notes field for the section
Here is what I'm experiencing when signing a document using this template
- When I choose a Yes option for a question in a section, the additional notes text field becomes required
- When I subsequently choose a No option for a different question in the section, the additional notes text field becomes not required
- If i then choose a different Yes option for a different question in the section, the additional notes field for the section becomes required again.
So on and so forth.
It seems like the conditional requirement is only applying based on the most recent selection, as opposed to treating each option's conditional requirements on their own.
how can i achieve this? or is this a bug?
Thank you!
Reply to: Condtional Requirement logic not working as expected
Monday, October 23, 2023 at 09:31amHi Dan,
I have filled in an Enhancement Request on your behalf, the reference ID is OSSSAAS-I-2175.
Duo
Reply to: Condtional Requirement logic not working as expected
Thursday, October 19, 2023 at 04:28pmHi Dan,
Thanks for the detailed information! This is very helpful!
Unfortunately, I don't think it's possible to achieve your goal with today's conditional logic. This is because like you mentioned, if multiple conditions are manipulating the same field, only the most recent condition get applied.
In order to achieve this goal, I think we need to fill in an Enhancement Request with a proposed solution, for example to allow below syntax in the conditional logic:
Condition:
Any radio button/checkbox/text field/etc. in a given list get selected
(It's opposite criteria is when none of the fields in the given list get selected, also makes sense)
Action:
Enable/Disable/Mark Require/Mark Optional a field/signature.
We can further extend it in a more generic way that if a list of conditions like "TextFieldA.value != null", "RadioButtonA.value == 'X'" has equal or less than N conditions meet the criteria then do the action, if more than N fields meet the criteria then do the opposite of the action.
Let me know your thoughts, and if you like the idea, I can fill in an Enhancement Request on your behalf and vote on behalf of your organization.
Duo
Reply to: Condtional Requirement logic not working as expected
Thursday, October 19, 2023 at 05:13pmHey Duo,
Dang! I was hoping that there was a way, but I understand. Yes, the feature request sounds great, thanks for putting that in!
Thanks,
Dan