Next button appears when revisiting but not selected

Hi Kimberly,

Welcome to Heroes! We would like to take a closer look at the issue. Please go ahead and submit a Support Case, making sure to upload your files when doing so.

Always Happy to Help,

Adrian

I'm having the same problem? What's the solution?

Hi Carole!

This thread is a bit dated and I do not see where Kimberly submitted a support case.

Can you share some details about the issue you are experiencing and perhaps share your .story file so that we can take a look?

Thanks for getting back to me so quickly.

I have a slide with a quiz question. At first, I simply hid the NEXT button, and when it reappeared after the user hits SUBMIT, it didn't work. Obviously, that's because I don't have a trigger attached to it. I couldn't figure out how to use a variable to direct it.

Next, I tried activating the NEXT button on the Slide Properties but added a trigger to hide it until the user correctly answers the quiz question. That didn't work either. I guess I didn't set the trigger and variable correctly, and after reading more about variables, I'm still not sure how to do it properly. Here's what I did:

Should I use States instead?

I appreciate your help.

Did you mean to include a file here for me to take a look at Carole? I'm not seeing one. If you are replying via e-mail, that could certainly be why.

Please be sure to click view to pop into the forums and utilize the 'Add Attachment' option in the bottom left of the reply window.

I'm attaching the screen shot of the trigger I attempted.

Hi Carole!

Are you not able to share a copy of the .story file for us to take a look? I would like to understand why you wish for both a Submit button and a Next button to be on the slide. 

Typically a Next button is not present on the slide as you can see in the sample attached.

I can probably share the file if necessary. But in a nutshell, I added the Next button because the Next button that automatically reappeared after the slide was revisited doesn’t work. (After all, how can you add a trigger to a Next button if it doesn’t show up in the Trigger panel?) That’s why I made it active, then tried to add a trigger to hide it until the user completed the question. That doesn’t work either. There must be a simple solution that I’m overlooking.

Did you take a look at the file I shared above? You are welcome to compare it to your set-up as the Next button post assessment seems to work fine.

Otherwise, yes, I'd like to understand your set-up so that I can further assist. 

If you cannot share here in the forums, you are welcome to share privately here.

I appreciate the example. I can see how you got the Next to work ... it goes to the results slide, which I don't have. Mine should just go to the next slide/scene. I've attached the file. If you can tell me where I went wrong, I'll be very grateful.

Hi Carole!

Thanks for sharing and allowing me to take a look. Since you were trying to hide this button, I assume you do not want the user to 'skip' over it, correct?

The issue being if the user utilizes the Prev button and gets back to that slide and then they are stuck?

You can add a trigger for the Next button that comes up during the review process, but it's a bit of a trick.

Copy the default Next button trigger, then you can delete the Next button from the slide properties, and then paste the trigger back in the trigger panel. You may want to actually set it to the specific slide since it is a new scene.

I've attached your updated file if you'd like to take a look and see if this is what you were looking for.

PERFECT! Exactly what I want to happen. I would never have figured out that trick on my own. Your help is much appreciated!

Hi - sorry this note was so long ago. I'm glad they were able to help above.

On that course, I did eventually just activate the next button to appear if it was on a quiz question that needed to jump to a new scene so they weren't trapped. I then did an error trap message layer to pop up if they tried to click next but not complete activity, yada yada.  

To be honest, lately I (and all of my fellow developers) don't use the next/prev buttons as provided in Storyline in our courses. We use our own custom onscreen buttons. It saves a ton of headache and gives us much more flexibility to control. Easier to make the next button only appear after an action has taken place etc, instead of all the variables to make the next button function at a certain time and need for an error trap layer.   It also gets rid of the new problem on lockdown player mode - that forces the learner to have to wait for the timeline to end before proceeding. (There is a storyline community post-publish workaround for that - but its a pain).  

The error trap message is an interesting workaround I hadn't considered. For consistency, my group has been told to stick to the default player navigation for the current series we're developing, although I suppose I could create my own buttons that simply look like the defaults.

This discussion has been very helpful. It boosts my confidence in using Storyline. Thanks to all! 

So glad to hear that Carole :) Glad I could assist too.