Disable Back and Next buttons on question slides

Hi Steve! Would you be able to share your .story file for us to have a look?

Thanks Leslie. A stripped down .story file with the behaviour is attached.

One issue might be that I still use the Articulate Submit button instead of a custom one.

Hi Steve, 

When learners review a quiz (or revisit question slides they've already submitted), they'll see Articulate Storyline's built-in Prev and Next buttons in the lower right corner of the player—even if you've disabled them throughout your course. These navigation buttons are necessary for learners to review quiz slides.

If you'd like to have an option to disable the Prev and Next buttons during quiz review so you can use your own custom navigation buttons, please let us know. We value your feedback.

Thanks Ashley. Good to know.

Hi,

Can anyone tell me how long it will take for this feature to be removed?

The whole aspect of "—even if you've disabled them throughout your course." seems totally ridiculous to not give the user the option to remove it.

I cant think of any good argument for it. Users should always have the option.

These have just appeared over the top of my usual next and back buttons to the point where it looks so ridiculous that I am either going to have to build my own question using triggers or rethink what software it is built in. - This is how bad an idea it is.

Thanks,

Elliot

Hi again,

I have found a work around for people who are struggling with this issue.

DO NOT remove the freeform. I did and it automatically deleted all of my multiple feedback layers. Luckily I noticed straight away.

Keep the freeform question but instead of adding the "Submit interaction" to the submit button, you create a "show layer" trigger for each layer to the submit button.

So you create a trigger on your submit button calling "Feedback 1". Then add an "if" statement to that trigger, stating:

if "option 1" is equal to selected.

Continue for all the other options.

This works exactly the same just without the unwanted/unneeded/crazy next button bug.

Hope this helps,

Elliot

Hi Elliot,

Thanks for sharing your workaround and thoughts here. I don't have a time frame to offer in regards to when this may be implemented as a feature within Storyline, as currently it's by desgin (not a bug). So please also share your thoughts in the form of a feature request so that it routed directly to our product development team and they can use that as they look towards future versions/updates of Storyline. 

Hi Ashley,

Thanks for the reply.

I just cannot understand any reasoning behind it, at all.

If a user has removed the inbuilt next and back buttons for their course then they MUST have their own navigation buttons. It just seems crazy to me, as if its a bug that has been passed off as a feature until enough people object.

I am sorry to object so strongly, but it is a feature that could be missed by developers on testing, which would look really bad to a client, especially when I cannot justify it to them.

I will continue to use the workaround for now though.

Many thanks Ashley,

Elliot

Hi @Elliot,

I'm confused with your work around; could you post your example on how to do this?

Hi Katie,

I've been having the same problem, and the workaround Elliot mentioned above is easy to replicate (once you've built the first one).

You have your base slide, correct slide and incorrect slide. Your submit button, when clicked, runs 2 triggers, one which opens the correct slide, the other which opens the incorrect slide; each of these triggers needs a condition adding to them -

Correct trigger
"if [correct element] is equal to selected"

Incorrect trigger
"if [incorrect element] is equal to selected or if [incorrect element] is equal to connected"

That's about it, you can then add a trigger onto the correct slide to increase the score of your quiz (if it is a recorded quiz). You can get the variable used for this by looking at your list of variables.

Now, doesn't it seem silly to have to do all that, just to get around one "feature".

Edit: You need to be careful with this when creating a "pick many" question, as states are not tracked properly in Storyline. You may have to set the triggers to "if [incorrect element] is no equal to normal"... another fun "feature".

Hi Katie,

Yes as Gary posted above.

I hope it works out for you.

Many thanks,

Elliot

Also,

My version has the trigger

"if [correct element] is equal to selected"

for each option as I have a unique feedback layer for each one.

You can use Gary's version above if you have a simple "correct" or "incorrect" question with just the two layers.

Many thanks,

Elliot

Hi Elliot, 

Happy to have the feedback and discussion in regards to the features and navigation - and I can understand how it may seem to be a bug, but this is working as designed. Even though you've added your own navigation buttons, on the quiz questions next/prev buttons aren't included the first time through by default as the user has the "submit" button. As it's currently designed, Storyline doesn't "know" that you have your own navigation buttons so includes next/prev buttons on a revisit/review so that the user isn't stuck in terms of navigating. At this point the best option is to share your thoughts in the form of a feature request with our product development team. 

Hope that helps clarify, and please let us know if you have any other questions. 

Hi Ashley,

I appreciate the replies, I will just work around it for now.

Many thanks,

Elliot

Thanks @Gary and @Elliot! I'll have to give it a try.