Back button functionality? Simple but important question.

Hi

Simple question(s). How does the default back button work? Can it be made to work "linearly?"

My testing shows clicking back does not take you to the prior slide in a linear course, but to the slide you just viewed.

For instance. If I have a 10 page course and on page 1,  I use the menu to jump to page 10, clicking 'back' will return me to page 1, not page 9. I.e. it returns me to the page last viewed (page 1), not the adjacent prior page (page 9)

Is this correct?

If so, can the functionality be altered for it to work in a linear fashion in which it takes you to the 'adjacent' prior slide, whether you just viewed it or not? I.e. in my example above, clicking back would take you to page 9.

Thank you

5 Replies
Nancy Woinoski

The pre button is designed to take you back to the last slide you viewed. It works the same way as the back button in a web browser.

You can change the trigger for the prev button to go to any slide you want but you have to do this on each slide. There is not way to make a global change to have the button go back in a linear path.

Dave Ray

Thanks for your reply, Nancy. I appreciate it.

But, oh man, not going to lie, this is very disappointing. That is quite non-standard behavior for the previous button on a course creation tool. The way it currently functions it follows the hyperlink model, not the linear progress model. At a minimum, I believe there should be a switch to enable the previous button to move the user to prior adjacent page.

Let me give you an example. I have a 100 page e-learning course for doctors. It is open navigation, and is meant to be completed linearly, though users are encouraged to explore as per adult learning principles.

If, on page 5, the user looks at the menu and chooses to jump directly to page 62 to explore a topic. They arrive at page 62, click forward a few pages, then back a few pages and then 'bam' they're back at page 5! They're going to go: "What the heck just happened?" Everyone is accustomed the previous button taking you to the adjacent page, not the last page your were on.

This is also disappointing news form a production standpoint, if the work around is to manually define a custom trigger on each previous button on each page? What if you re-order your pages and drag a page into a new scene or new sequence? Your trigger will no longer work. You will have to constantly remember to modify it, reducing the usability of Storyline in general.

Wow, surely I can't be the only one that sees that as an issue? There really needs to be a switch to enable automatic adjacent page navigation.

Nancy Woinoski

Dave Ray said:

Thanks for your reply, Nancy. I appreciate it.

But, oh man, not going to lie, this is very disappointing. That is quite non-standard behavior for the previous button on a course creation tool. The way it currently functions it follows the hyperlink model, not the linear progress model. At a minimum, I believe there should be a switch to enable the previous button to move the user to prior adjacent page.

Let me give you an example. I have a 100 page e-learning course for doctors. It is open navigation, and is meant to be completed linearly, though users are encouraged to explore as per adult learning principles.

If, on page 5, the user looks at the menu and chooses to jump directly to page 62 to explore a topic. They arrive at page 62, click forward a few pages, then back a few pages and then 'bam' they're back at page 5! They're going to go: "What the heck just happened?" Everyone is accustomed the previous button taking you to the adjacent page, not the last page your were on.

And the work around is to custom trigger each back button on each page? What if you re-order your pages and drag a page into a new scene? You're trigger no longer works? You have to keep editing it? This is also very non-standard.

Wow, surely I can't be the only one that sees that as a big issue? There really needs to be a switch to enable automatic adjacent page navigation.


You are not the only one. I suggest that you put in a feature request. The more people that put in a feature request the better.