Forum Discussion
I can't seem to get the trigger 'When the state [BUTTON A] is Visited' to work.
I'll also add, if you explaine dmore abnout exactly what you want to do, that may help inform a better solution.
For example, I'm curious about why they get from one slide to another to visit buttons and then why they come back to the other slide to unlock the continue button.
- MichaelWest6 months agoCommunity Member
Fair question, Tom.
I'm in sales training, and I am creating an e-learning module for our field reps that will introduce them how to use our discovery form for when they're meeting with potential clients for the first time. This form comprises 4 separate sections, and one of these sections, the one I'm working on now, has 9 separate products for which they need to understand what initial questions to ask, what follow-up questions that might ask, and how to position the product.
It's a lot, I know.
I wanted to break it up into 9 smaller modules, but my SME doesn't seem to want that. (Of course, they don't.) So, I'm using a primary menu (the base layer of that one slide in my example) with a button for each product. Each button will direct them to another layer with the details for that product.
I might try and just use separate slides instead, as that seems to be the easiest way. I'm just trying to save a little real estate on the screen.
However, I'm also hoping that, when the SME sees the final result, they will come around to the idea of 9 separate modules.
We'll see....