Visited States

Fix Issue #1:

1. Set slide properties to Resume saved state

2. For all hotspot click events, change the order of triggers so that the state change (e.g., setting a button to Visited) occurs before the Jump to slide trigger. Example:

Fix Issue #2:

Why use this trigger? Instead of jumping to the same slide, you can simply hide the layer by clicking the Back button to return to the base layer. Using a trigger to jump to the slide will reset all progress—for example, if a button is set to Visited, jumping to the slide will reset it to Normal, unless the slide's properties are set to Resume saved state, which is unnecessary in this case.

Change the trigger on all layers to: Hide this layer when the Back button is clicked. This way, your trigger to change the Next button state to Normal will work as expected.

Overall Improvement:

I've attached a cleaner version of both slides, this time without the hotspots. I kept the text boxes, as each already has a Visited state applied. Clicking a text box automatically activates its Visited state without the need for additional triggers. Overall, all redundant objects such as hotspots and their associated triggers have been removed.

Based on what I see in Review 360, here's what I suggest:

Don't use hotspots. Instead, have the desired triggers run when the user clicks the labels. Because you already gave those a Visited state, each one will change automatically to Visited when clicked. In other words, the labels are your buttons.

When the user doesn't leave the slide, you can use the objects reaching the Visited state as the "when" in a trigger. Here's an example:

 

When the user jumps to other slides and then returns to the slide with the buttons, use a "when the timeline starts on this slide" trigger with conditions to control the Next button. Here's an example:

• Notice that the conditions are connected with "or." That means the action will be performed (e.g., Next will be disabled) if any condition is met.
• A "when the timeline starts on this slide" trigger will run every time the user visits a slide. That's true even if the Slide Properties are set to "Resume saved state." 

 

For additional info:

• TIP: Controlling the NEXT Button 101 | Articulate - Community
• TIP: Create a Custom Menu Slide | Articulate - Community 
• PRIMER: Hotspots vs. Transparent Shapes | Articulate - Community (for when there aren't separate labels or other objects for the user to click)

OK, I looked at Major Muscle 1 and see how it works. The next button didn't work for me, so I jumped to the next slide by clicking on the menu to Major Muscle 2 and see as I click on the body areas there is no change in States. First, I would check and if needed check your states on the second slide. It may be going to Visited, but the Visited state may be the same as Normal. 

Next, I don't like using/adding a Next button. I like to restrict the Menu, so the standard Next button is not active until the timeline is done. I change the Next trigger to switch from Inactive to Active after all layers have been visited. 

Good luck, if you need any just reach out.