Forum Discussion
Storyline 360: Next button enable in SCORM output is not working as expected
Hi all,
I created a page in Storyline 360 with three tabs, each having a corresponding layer that displays content when the tab is clicked. When the user enters the page, the Next button is initially disabled by changing its state.
To enable the Next button, I check whether all three tabs have been visited by using three variables: Tab1, Tab2, and Tab3. On each respective layer, I set the corresponding tab variable to True. I then added a trigger to enable the Next button by checking whether all three variables are set to True. For example, the trigger for Tab 1 checks whether Tab2 = True and Tab3 = True, and if so, changes the Next button state to enabled.
This functionality works correctly when I publish and review the course in Review 360. However, after publishing the course as SCORM and launching it from the LMS, the behavior is inconsistent on some tab pages. The Next button gets enabled even when only one tab is clicked.
Has anyone faced a similar issue? If so, could you please suggest how to resolve it?
6 Replies
Are you resetting the variables between slides? You would need to set them all to false each time a slide loads unless they are unique variables for each slide.
To be honest you dont need to use variables, this is simpler to do with visited states.Hi PhilMayor,
Thank you. I am not resetting the variables between slides and using the same variables in multiple slides. Do you suggest on entering a slide, set the variable to false? Also, can you show some light on how to do with visited states?
It’s an odd issue that I don’t think I’ve experienced before. If your logic and triggers work in Review, I don’t see any reason why they wouldn’t work in the LMS. Have you tried publishing to Web or testing in SCORM Cloud to see how it behaves there?
Would you mind sharing a simplified version of a few slides so it can be troubleshooted?
However, I would agree with PhilMayor's suggestion and rely on visited states instead. You could use a single T/F variable (e.g., slideVisited) that becomes True when all objects are visited, along with a trigger that changes the state of Next to Normal once all objects have been visited. Then, use a timeline start trigger to disable Next if slideVisited is False; otherwise, change the state of Next to Normal to ensure it remains enabled upon revisit.
Thank you PhilMayor and Nedim. So do you suggest to set the variable to false when the layer begins? Sharing the screenshot to show my current setup.
Your current setup assumes the learner only needs to click one of the buttons to enable Next, depending on which is clicked first.
I assumed your intention was for learners to click both buttons and view both layers before enabling Next, and that Next should remain enabled when revisiting the slide. In that case, you can rely on visited states instead of variables. As each button is clicked, it automatically changes to its built-in Visited state (no triggers needed).
Once both buttons are in the Visited state, you can:
- set a variable (e.g., slideVisited) to True
- enable the Next button
The variable is only needed if you want Next to stay enabled upon revisiting the slide. If you prefer Next to reset (be disabled again), then you don’t need a variable at all. The trigger to ensure Next is disabled only the first time the learner visits the slide should be set to run when the timeline starts, with a condition (e.g., slideVisited = False).
If you leave it without a condition, the Next button will appear disabled every time the slide is visited.I’ve attached a simple example file to illustrate this approach, along with the triggers used to ensure Next is enabled once both buttons reach the Visited state.
