'Jump to' trigger jumping to layer and not the base slide

Jul 19, 2018

Hi there,

I'm currently working in Storyline 360. I have a project with multiple scenes. The main scene has six team task slides, and for each task slide there is a corresponding quiz/question scene.

On the base layer of each team task slide are the listed tasks.

 

When a task is clicked the relevant task layer is shown.

Each task layer has four buttons - one is a 'Test your understanding' button. When the 'Test' button is clicked the learner jumps to the relevant question scene. 

Within each question is a button called, "Pick another task". The purpose of this button is to go back to the relevant task (base) slide (image 1). I'm using the 'Jump to slide' trigger but the module jumps to the task layer (image 2), and not the base (image 1). The client has tested the published module on their LMS and the same thing happens (jumps to the layer instead of the base slide).

Any thoughts on how I can force the module to jump to the base slide, bypassing the layer?

Thank you in advance.

7 Replies
Wendy Farmer

Hi Kerry

still - I suspect if it's opening up on a layer that means that the layer wasn't closed after it displayed the first time.

There aren't sneaky triggers on the master slides that might be causing angst?

 Can you strip out some of the content and send through a sample few slides - hard to say without seeing the setup.

Kerry Sheehan

Ahhhh ... I see what you did there! Adding a 'Hide the layer' trigger to the 'Test' button is a brilliant idea. I notice that there's a flicker of the base slide before it jumps to the question slide. So I thought I'd try changing the order of the triggers for this button (to 'Jump to slide' first, and then 'Hide this layer'), it does stop the flicker but the same issue occurs (from the question slide it jumps back to the layer, not the base).

Thank you so much for your solution. I'll keep playing with it, I'm sure I'll find a way to make it work now that you've got me out of my little rut. Thank you again.

This discussion is closed. You can start a new discussion or contact Articulate Support.