Navigation on interactions

I'm having trouble with navigation on interactions. I have it set up to show a feedback layer when the user clicks the Submit button, and it looks like the layer flashes and then another screen displays.

I can't figure out 1) where this navigation is coming from (see red circle) and 2) why it isn't showing the layer properly. Any help would be appreciated.

3 Replies
Ashley Terwilliger

Hi Sheryl,

You only see that arrow when you've clicked on the slide 1.8 as 1.9 would be the next one in the regular order - but testing your file, everything seems to progress as the triggers have been set up.  You may want to review this tutorial on how to use Story view, and this one on how slides are numbered and shown within Story view. 

Sheryl Houston

I know when the arrows display in Story view; my point is that there is no reason for that arrow to be there - all of the naviation points to a different screen. I'm afraid these tutorials do not answer my question. When I run the lesson it does not work as the triggers are set up. The Submit buttons are supposed to show a layer, not jump to a different screen, and that's what happens when I test it.

I'll submit a ticket instead of using the forum.

Ashley Terwilliger

Hi Sheryl,

You're always welcome to submit a ticket or use the forum - either way we can assist.

When I take a look at your lesson again and looking at your triggers - I see that the slide shows the layer quickly and then jumps to the slide that it is supposed to. When trying to add a trigger to the layer itself, such as to hide the layer it doesn't always seem to keep the trigger I've created which is not the expected behavior. I am able to see the layer without the quick jump to the next slide when I click submit prior to answering the question. Since it's behaving oddly, I'm curious if you're adhering to these general guidelines for working with your Storyline files:

  • Work on your local drive (your C: drive).Working on a network drive or a USB drive can cause erratic behavior, includingfile corruption, loss of audio, and other unexpected behavior.
  • You should also make sure the directory pathto your project files and your published output is less than 260 characters(for example C:\Articulate).
  • Avoid using special characters, accents orsymbols in your file names.

Please let me know if you've submitted a case and if you have the case number handy so that I could follow along in that too.