Forum Discussion
Conditional logic is silently removed after accessing Quiz Settings
Steps to replicate:
- Create a quiz with a results page.
- Add conditional logic which only shows the "Success" layer when:
Quiz1.ScorePercent is greater than Quiz1.PassPercent
*and*
Quiz1.ScorePercent is less than 100 - Go to Design tab and click Quiz Settings button
- Click "OK" without making any changes.
Observation:
The 2nd condition will be removed, and the first condition will revert from ScorePercent to ScorePoints.
I have replicated this on two different computers. Storyline version 3.92.33293.0
Demo file attached.
I'd be very grateful if someone could attempt to replicate this.
Many thanks in advance.
- NedimCommunity Member
I was able to replicate it. Storyline version 3.92.33293.0
Hi DeveloperIgniti,
I'm happy to replicate these steps to determine whether this is related to a product defect. I created the attached Storyline file and applied the abovementioned steps. I used the same Storyline version as you and Nedim and saw a different result. The trigger conditions were unchanged. Here's a quick screen recording of my replication attempt.
Did you see something different from how I executed the steps? There could be a difference in Step #2: "Add conditional logic which only shows the Success layer." I turned off the built-in trigger and added a new one.
I am looking forward to your response!
- DeveloperIgnitiCommunity Member
I replicated your steps and can confirm if you disable the default action and create a new custom action containing the conditional logic, the issue does not occur.
However, if you then delete the default action, the problem reappears.
Hello DeveloperIgniti,
Thanks for the additional information. I was able to recreate the issue with the extra steps provided. I've filed this as a possible bug with our product team. This community thread is included in the bug report so we'll notify you as soon as we have any updates to share. Thank you for bringing this to our attention and we apologize for any inconvenience this bug may have caused.