How do I keep the learner from advancing to the next slide, until they have looked at all the layers on the slide?

I am building a compliance course in Storyline. I have several buttons on the slide that reveal layers with content. I'm trying to figure out how to keep the learner from advancing to the next slide until they have at least opened all the layers. Currently, I have it built so they can choose the buttons in any order they choose.

Can anyone help me?

Ruth-

10 Replies
Wendy Farmer

Hi Ruth

you could add a trigger to disable the next button when the timeline starts (very first trigger in the list)

and then create another trigger to change the state of the next button to normal when the state of all your buttons are visited or completed (depends what states your buttons have).

You could also use variables - let me know if the above will work for you, if not and you want to upload your story file we can show you how to do it.

Jackie Van Nice

Hi Ruth!

I've been working on a project where this same requirement is included, and my solution is very much like Wendy's: I've set the next button's initial state to invisible and added a trigger to change its state to normal once X, Y, and Z (your layer's buttons or whatever you're using) have all been visited. Works like a charm!

Ruth Simmons

Jackie,

Thanks! I went another way by creating conditions for the Next button, but a really appreciate your response.

Ruth-

RUTH SIMMONS Senior Curriculum Developer
MN Contact Center TCF Bank 1405 Xenium Ln N, Ste 220 * Plymouth, MN 55441
P: 612-661-7917
rsimmons@tcfbank.com

----------------------------Disclaimer----------------------------
This email may contain privileged and/or confidential information that
is intended solely for the use of the addressee. If you are not the
intended recipient, you are strictly prohibited from disclosing, copying,
distributing or using any of the information contained in the transmission.
If you received this communication in error, please contact the sender
(“Company”) immediately and destroy the material in its entirety,
including all electronic and hard copies.

This communication may contain nonpublic personal information about
consumers which is subject to restrictions under the Gramm-Leach-Bliley
Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse
or disclose such nonpublic personal information for any purpose other than
to provide the services for which you are receiving the information.

There are risks associated with the use of electronic transmission. The
sender of this information does not control the method of transmittal or
any service providers and the sender assumes no duty, liability, or
obligation for the security, receipt, or any third party interception of
this transmission.

The Company reserves the right to amend statements made herein in the event
of a mistake. Unless expressly stated herein to the contrary, only agreements
in writing signed by an authorized officer of the Company may be enforced
against it.

Judy Nollet

I suggest changing the state of the NEXT button to Disabled -- not to Hidden. Why? When NEXT is hidden, the PREV button moves into its place. If a learners is holding the mouse over that position and clicking without paying attention (as we all know some of them do), they'll go to the previous slide and likely be confused about what happened.

David Anderson

Hidden vs. disabled button states is a question that comes up frequently in our workshops. 

I think you can go with either disabled or hidden buttons as long as you're consistent. What I see happen a lot is designers will make one tabs slide optional and then the next conditional. Same design for both, only they hid the next button on the conditional slide.

My design preference is to disable persistent objects that are normally available like the submit and next buttons. The user already knows where to find those objects, but sees the objects are acting different on conditional slides.

Using a small tooltip on rollover also helps to explain why an element is inactive.

Ruth Simmons

Thanks David. I appreciate the help.

RUTH SIMMONS Senior Curriculum Developer
MN Contact Center TCF Bank 1405 Xenium Ln N, Ste 220 * Plymouth, MN 55441
P: 612-661-7917
rsimmons@tcfbank.com

----------------------------Disclaimer----------------------------
This email may contain privileged and/or confidential information that
is intended solely for the use of the addressee. If you are not the
intended recipient, you are strictly prohibited from disclosing, copying,
distributing or using any of the information contained in the transmission.
If you received this communication in error, please contact the sender
(“Company”) immediately and destroy the material in its entirety,
including all electronic and hard copies.

This communication may contain nonpublic personal information about
consumers which is subject to restrictions under the Gramm-Leach-Bliley
Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse
or disclose such nonpublic personal information for any purpose other than
to provide the services for which you are receiving the information.

There are risks associated with the use of electronic transmission. The
sender of this information does not control the method of transmittal or
any service providers and the sender assumes no duty, liability, or
obligation for the security, receipt, or any third party interception of
this transmission.

The Company reserves the right to amend statements made herein in the event
of a mistake. Unless expressly stated herein to the contrary, only agreements
in writing signed by an authorized officer of the Company may be enforced
against it.