State of Next button on a revisit

Have a look at the attached and see if that's what you wanted. I added conditions to the trigger that disables the Next button to only execute if any of the buttons is not in Visited state. Theoretically you only need one button as a condition, but for completeness I added all of them.

Thanks Michael, going to take a look now, will let you know!

This is great, I don't think I would have thought of this.  Just one question, I had left the slide properties when revisiting "Resume saved state"  is this the best one still to go with or should I change it back to "Automatically decide"...or does it matter.

Thanks so much, I did try for a day or so to try to figure it out, but I guess I need more practice.

Cheers to you for taking the time to show this to me, greatly appreciated!

For this particular slide setup, it shouldn't make a difference. Have a look at these descriptions of the various revisit options here.

Okay, I get what you are saying for this instance it doesn't matter.

Thanks again!

Michael, hey there it was a year ago you helped me with this.  And of course it happened again. I was sure I had done in right, then went back here and saw that you had triggers for Not visited and Visited.  When I was doing it this time, I thought just stating to have it normal if they are all visited, why wouldn't that be enough, how come we had to do the not visited part....wondering if you can explain, as I am glad it works on my new elearning but don't see why just the "Set Next to Normal if they are all visited" wouldn't work....hmmm

Hi Teresa,

I'm not Michael, but I can take a stab at explaining this one.

The trigger that includes the "Not Visited" is specifically for the Next button to be disabled when the timeline starts. This allows the conditions to determine if the Next button should be disabled. Without the conditions, the Next button is disabled at the timeline start regardless after visiting other slides as you encountered.

The trigger that includes the "Visited" is specific to the buttons on the slide. This is insurance so that the Next button becomes enabled when the user is still on the slide and all the buttons have been visited - because the timeline has not restarted in this instance.

One is a slide trigger and one is an object trigger:

Hope that helps :)

Well Leslie, I appreciate it,  I will keep this bookmark as a reminder, if I don't do things enough in storyline, I sadly am always re-teaching myself :)  Getting older....lol!

No worries, Teresa. I'm learning every day as well :)

Hi Leslie,

I was facing the same issue and the solution you helped me achieve my objective. Thanks a ton :)

That's great news, Indrani. I appreciate you popping in to share and welcome to E-Learning Heroes. 😊

I appreciate the fact that this thread exists, but it was driving me crazy, trying to figure out why my "Next" button remained disabled even though I thought I was adding the correct logic by enabling the Next button when "All" of the object buttons on my screen were disabled. But lo and behold, every time I revisited the slide, after clicking on all the buttons, the Next button remained disabled!

Why shouldn't objects be able to trigger the slide functions? Or maybe a better question for your developers, from a user POV, if an object can't change the status of a slide on revisit, Storyline should let you know.

Anyway, thank you Leslie for the explanation. It looks like I'll get to keep some hair on my head today. lol