When reviewing my SL360 quiz I see in the corner: < prev next > When clicking prev or next just very shortly submit is visible. How can I stop the submit from showing. Thanks, Mia.
That sounds an issue indeed. I'll do my best to help.
If you haven't done it yet, may I ask you to check if the "submit" button is disabled on the slide properties? You can use the image below as a reference:
If that doesn't do the trick, you may share your .story file here if you're comfortable with it and I'll take a look at it further. You can also send it privately to Articulate's Support Team at https://articulate.com/support/contact/case
I hereby send a test-story. My original story has 10 questionbanks with many questions. That story is a little bit slower so the submit is easier to spot. But previewing this test-story gives the submit in the review also. Thanks.
I've been playing around with the file for a few hours and this seems to be a tricky one. Here are my findings:
1. The "submit" button is from the slides on the question bank. (Tested by changing the state of the submit button through triggers)
2. The "submit" button is automatically replaced by the "prev / next" button during review.
3. Disabling the "submit" button inherently causes the "prev / next" button to disappear as well during review.
What I tried:
I tried to "change" the "state" of "submit" button on the slide to "hidden" but I am having an issue with the "when" variable. Having the trigger go off at the start or end of the timeline applies it right away so you won't be able to submit the answers. Having it trigger after clicking the "submit" button doesn't work as well. Setting conditions on when to apply the trigger doesn't seem to work as well.
I tested this by enabling the prev / next buttons and manually going back through the slides without entering the review mode. "Submit" button still appears briefly.
Conclusion:
Although I am not entirely sure, this could be a bug on player's navigation button and is something that we might not be able to resolve naturally.
Suggested Workaround:
1. Use a custom button for submit and add a trigger for the submit function and validations on when it should work (since the user can still go back to the base slide during review). You need to do this on all the slides within the question bank.
2. Disable the player's default submit button on each slides within the question bank.
3. Enable the next / prev button on the results slide (so that you can navigate during the review)
Note: It is quite a bit of work because of the triggers and validations that you have to set but it's the only workaround I can think of at the moment. Other users on the forum might have a better idea so I am leaving the floor to them.
I hope that you can find use to this and please do let me know if you have questions.
Thank you very much. I wonder how the submit-button got into the questions in the questionbank. Maybe this happened when questions where copied from a story to a questionbank.
There are more than 1000 questions and a complex workaround is not an option right now. So I let the submit blinking in the review. Maybe I'll look into this some other time.
You are very welcome and I understand that the complexity of it is not an option indeed.
I recommend submitting a possible bug report at https://articulate.com/support/contact when you have the time so that we can possibly have a more permanent solution to it.
With that said, I wish you all the best with the project and please do let me know if I can be of any further assistance.
6 Replies
Hey Christien,
That sounds an issue indeed. I'll do my best to help.
If you haven't done it yet, may I ask you to check if the "submit" button is disabled on the slide properties? You can use the image below as a reference:
If that doesn't do the trick, you may share your .story file here if you're comfortable with it and I'll take a look at it further. You can also send it privately to Articulate's Support Team at https://articulate.com/support/contact/case
I hope this helps. Regards,
Jaycee
Hello Jaycee,
I hereby send a test-story.
My original story has 10 questionbanks with many questions. That story is a little bit slower so the submit is easier to spot. But previewing this test-story gives the submit in the review also.
Thanks.
Hello, Christien,
Thanks for the file. I was able to download it and I am now investigating what's causing the issue. I'll let you know as soon as I find anything.
Hello, Christien,
I've been playing around with the file for a few hours and this seems to be a tricky one. Here are my findings:
1. The "submit" button is from the slides on the question bank. (Tested by changing the state of the submit button through triggers)
2. The "submit" button is automatically replaced by the "prev / next" button during review.
3. Disabling the "submit" button inherently causes the "prev / next" button to disappear as well during review.
What I tried:
I tried to "change" the "state" of "submit" button on the slide to "hidden" but I am having an issue with the "when" variable. Having the trigger go off at the start or end of the timeline applies it right away so you won't be able to submit the answers. Having it trigger after clicking the "submit" button doesn't work as well. Setting conditions on when to apply the trigger doesn't seem to work as well.
I tested this by enabling the prev / next buttons and manually going back through the slides without entering the review mode. "Submit" button still appears briefly.
Conclusion:
Although I am not entirely sure, this could be a bug on player's navigation button and is something that we might not be able to resolve naturally.
Suggested Workaround:
1. Use a custom button for submit and add a trigger for the submit function and validations on when it should work (since the user can still go back to the base slide during review). You need to do this on all the slides within the question bank.
2. Disable the player's default submit button on each slides within the question bank.
3. Enable the next / prev button on the results slide (so that you can navigate during the review)
Note: It is quite a bit of work because of the triggers and validations that you have to set but it's the only workaround I can think of at the moment. Other users on the forum might have a better idea so I am leaving the floor to them.
I hope that you can find use to this and please do let me know if you have questions.
Hello Jaycee,
Thank you very much.
I wonder how the submit-button got into the questions in the questionbank.
Maybe this happened when questions where copied from a story to a questionbank.
There are more than 1000 questions and a complex workaround is not an option right now.
So I let the submit blinking in the review.
Maybe I'll look into this some other time.
Thanks again.
Hey, Christien,
You are very welcome and I understand that the complexity of it is not an option indeed.
I recommend submitting a possible bug report at https://articulate.com/support/contact when you have the time so that we can possibly have a more permanent solution to it.
With that said, I wish you all the best with the project and please do let me know if I can be of any further assistance.
Regards,
Jaycee