Trigger Help for Restricted Next Button

Dec 13, 2018

Hi Articulate,

I just wanted to ask if there's a way to make my custom Next button appear after all accordion tabs have been visited/viewed, given that the motion path/animation setup for this interactive page is not as simple as I thought it would be in terms of just adding triggers and such.

I've attached my sample for your reference and would really appreciate it if you can help me out. For now, I've placed the custom Next button at the very last tab (slide layer).

Take note that I've already tried tinkering with the slide layer properties and placing an additional slide layer for the Next button--but they don't seem to work for me given this setup.

Thank you!

Regards,

RJ

7 Replies
Roberto Joshua Malazarte

P.S.

If you try to play around with the sample interaction that I attached, the custom Next button won't appear even with the following triggers/settings:

1. Next button in its own slide layer; then add a trigger in the base layer which shows the layer when any/all of the tabs are visited.

2. Next button with an initial hidden state in the base layer; then add a trigger which enables the objects (since it's a custom Next button) to be visible (Normal) when any/all tabs are visited.

Thanks!

Patrick Nolan

Couldn't really figure out a working example/demo, I know the interaction on a single slide is probably preferred however if all else fails a more linear analog approach could meet your goal. Each accordion as an individual slide, good reference from an older Articulate Challenge:

http://articulate-storyline-samples.s3.amazonaws.com/butterfly-life-cycle-optimized/story.html

Link to the full challenge:

https://community.articulate.com/articles/accordion-interactions-in-elearning

If i can get my demo attempt to work I will post.

Patrick Nolan

 

As I was already working on Tabs interaction I continued with it but should translate to accordion. Apologies i couldnt work in your file my older update wont allow me to open it (I cant update either) Hope this helps.

Base layer has all tab buttons (states Blue normal, Orange hover, Gray Visited)

Base layer triggers show layer for each of the tab buttons

Variables alltabs Number starts at 0, alltabsvisited True/False starts as false

Each tab slide layer has all graphics and content with the the following triggers Add 1 to alltabs variable, Set alltabsvisited equal to true if alltabs is greater than or = to 5 (or number of slides)

Change state of Next btn to Normal when timeline starts if all visited is equal to True

Change state of Tab 1 btn to Disabled when timeline starts

Each next button  on the tabs has a empty disabled state. The buttons initial state is as disabled essentially hiding the button.

Learner can visit each tab one time which increase the alltabs count eventually tripping the alltabsvisted to true. As a result which ever tab is visited last will switch the Next btn state to normal making it visible.

I'm pretty sure the variables use could be better, if any of this isnt clear please feel free to reply and I will attempt to clarify.

Additional side note I am on an older update of 360, this could cause issues if your on a more recent version.

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