Trigger Help

Hi, Dominique_carr!

This sounds like some odd behavior and a bit inconsistent. Would you be willing to share you file with us here or privately in a support case? We'll delete it from our systems once troubleshooting is complete!

I suggest using 99% transparent circle shapes instead of hotspots. Unlike hotspots, shapes can have a Visited state, which is a built-in feature in Storyline. This means you won’t need to create additional triggers to set the state. The Visited state is automatically applied when the shape is clicked, reducing redundant triggers and simplifying your setup. These redundant triggers and multiple object states could potentially be the cause of your issue.

Thanks for the suggestion, I tried that and it still didn't work. The next button changes to normal when the last icon (consequence) is clicked (as it should) and then the slide jumps to a layer. On this layer the next button is still visible. There is a learn more button on this layer that takes you to another slide. Once the user is done with that slide there is a button that is set to take them back to the main slide but instead takes them back to the consequence layer and that is when the next button becomes disabled again.

Dominique_carr​ : The "learn more" may be the problem.

I'm guessing there's a "Change the state of the Next button to Disabled when the timeline start on this slide" trigger. When the user leaves and then returns to the slide, that trigger will run again. Yes, even if the Slide Properties are set to "Resume saved state." 

Add conditions to the trigger so it won't disable Next on revisiting. Here's an example:

P.S. I agree with Nedim​. It's simpler to use transparent shapes instead of hotspots. 

So that fixed my next button issue when consequences is visited last but now my next button is triggering to normal when I click on any circle/icon. I am about to just disable certain sections to force the user to go in a specific order to help with the next button issue. I want them to have choice but this scene is giving me far too many issues.

At this point, it's virtually impossible to troubleshoot without seeing the .story file. If you want to upload a copy, here are the best practices for doing that: 

• Only include slides that are related to the problem.
• Be sure objects, layers, motion paths, and variables have meaningful names.
• If there is proprietary content, replace or delete it. For example, replace proprietary text with “ipsum lorem” text.

BTW, this post has a demo file that includes another way to control the Next button when you want learners to view layers: https://community.articulate.com/discussions/discuss/tip-controlling-the-next-button-101/873348.