This example illustrates how to disable next button when the timeline starts and enable next button when a variable change occurs after all of the slide buttons/objects have a state change to visited. Note: All buttons must have a visited state. The next button will be enabled if the slide is revisited. Step 1:Create a True/False variable for the slide objects visited (SlideNumb_Action_VariableType).Example Variable: Variable Name, Type = True/false, Default Value = False S1_AllObjectsVisited_TF Step 2:Create a trigger that changes the next button to disabled when the timeline starts if the variable is not equal to true.Example Trigger: Step 3: Adjust the variable when the identified slide elements change to a visited state.Example Trigger: Step 4:Change the state of the next button to normal when variable changes.Example Trigger:

Just wanted to chime in here for any future users who are desperately trying to make this work like I was only a few moments ago. In storyline360 you might not need to use variables at all.I don't fully understand them yet and I was getting a weird thing when if I left the slide and went back to it sometimes the next button was greyed out and sometimes it wasn't, it was very frustrating. My slide had three panels I wanted learners to click and read the information that came up in the layer that opened before moving on. All I did was:1. Set a trigger to change state of next button to disabled when timeline starts on this slide 2. Create a visited state for my panels and set a trigger for that (change state of rectangle to visited when user clicks on it) 3. Set a trigger to change state of next button to normal once all rectangles (the panels) had changed their state to visited. This works like a charm but it does have a few limitations. You must make sure you slide is set to reset to initial state when revisiting (or else the next button will always disable because of the first trigger) which means your learners will have to interact with your objects every single time which can be frustrating too. And, this works for things where you can trigger something due to a change in state, with more complex interactions you might have to find one more workaround on top of this. Anyway, just thought I would put this out there in case anyone needed it!

Hi Benedict, Here is another way you can do the same like Wendy did. The only difference is, you will see the visited/completed state after visiting the branching/inner slides. Attached is the Story file for your reference.

Place this trigger on the layers, as one of the actions when the Return to Menu object is clicked. If the layers can be visited at random, you need to place it on each layer, otherwise, just the last one. Without the file, I have no ideas about the audio file. If you could sanitize it, you could attach that slide here.

Thanks James for sharing those steps here! Sounds similar to another example we've documented here for Storyline 2.

Hello. I've used triggers like in the example you posted, Ashley, to set the Next button to not appear until the timeline reaches the end. This seemed to work fine, but I recently found out that if you hit the Enter button, it advances the slide without having to click the Next button. Also, when viewing on a tablet, the user can just swipe ahead before the Next button appears. Is there a way to disable this functionality so the slide can only be advanced by clicking Next when the button appears? I have searched the forums everywhere and can find out how to do this? thanks.

Disable Next Button on a Slide until all Buttons are Visited

LeslieMcKerchie
Staff
4 years ago
Hi Kylie,

I want to take a look at your project file to investigate what's happening with your permission. You can share it publicly here or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.
LeslieMcKerchie
Staff
4 years ago
Thanks for sharing your file, Kylie. I'll take a look and reply to you privately via email in your support case.
TeresaVanderpos
Community Member
4 years ago
There is some great information here. Just a note @ EMR the states and not variables is how I have always done it with no issues and then today, no matter what I do checked again and again it just won't work. So I searched for the issue and came upon this thread and the variable solution works. So, I am just glad to see there is more than one way to accomplish the same thing.

But very frustrating that the states technique for some reason just won't work on my file and I had a colleague check it....
WaltHamilton
Super Hero
4 years ago
"When states is" can be flakey. Among other things, in the past it was documented not to be able to handle more than four objects whose states were checked. I don't know if that has ever been remedied, but there are other problems with it, too. If there is a listener for states changing, it is very low priority or/and only listens sporadically. Variables actually are very reliable.
LaurenDuvall
Staff
3 years ago
Hello everyone!

We are no longer seeing this bug, Swipe next gets enabled when the Next button is enabled, in our latest version of Storyline 360. Please make sure you're using Storyline 360 (Build 3.61.27106.0) or later.

You can reach our Support Team in this discussion or privately in a support case.
JessicaChandler
Community Member
3 years ago
Hi, this workaround is working when i am in Storyline previewing but when uploaded into our LMS it no longer works. Any suggestions?
BillEdwards
Community Member
2 years ago
Hi. I've got v3.80 of Storyline 360 and I'm struggling to find up-to-date tutorials for achieving this.

I've only just started learning how to use Storyline and the tutorials I've found so far don't appear to match what I see in the version I have. For example, I don't have the 'all of' option in my Trigger Wizard. And the tutorials I do find seem to assume prior knowledge or come in after some other steps have been completed first.

Have the Trigger Wizard options changed radically recently?

Any pointers to up-to-date advice or tutorials would be great.

Many thanks.

Bill
- JoseTansengco
  Staff
  2 years ago
  Hi Bill,
  
  Happy to help!
  
  I've attached a sample file so you can see how the basic concept discussed in this thread works. Majority of the slide will function around the trigger shown here:
  
  And from here, you can add conditions to add more logic to the slide. Try adding three buttons to your slide and then copying the trigger above, you should see the 'all of' condition shown above. You can find more helpful articles on how to use Storyline 360 here:
  
  Storyline 360: Getting Started
  
  Also, I wanted to invite you to our tips and tricks webinars. Once each month at 11am ET, our training team hops on a live call to answer top questions from our customers.
  
  It's super casual (and they're super smart!), so it's a great place to get expert tips and answers to frequently asked questions from our online community. In short, everything you need to create incredible online learning! You can register for the next call here: https://articulate.fyi/3ZiKgu9
  
  And don't worry if you can't make it, because everyone who registers will get a recording sent to them afterwards! There's also a huge list of on-demand past trainings available.
  
  Hope to see you there!
  states.story118 KB