In Storyline 360, States help us change the formatting of objects as learners move through an e-Learning—from indicating which items are interactive, to which have been visited, or which objects aren’t yet available. We utilize states all the time in developing courses, not to mention that states are one of the foundational concepts in our hands-on Articulate 360 training. During Storyline 360 training, we learn to create custom states manually. However, while states are always simple to use, you might have premade graphics on hand that you simply want to
When we teach interactive elements in our hands-on Articulate Storyline 360 training, someone will inevitably ask: “How do we keep learners from interacting until the narration ends?” This can be crucial in compliance-based e-Learning, ensuring the learners receive all content and don’t skip ahead. Let’s look at ways we can temporarily lock interactions for this “as heard in training” question. As you’ll undoubtedly hear us say in training: “There’s always more than one way to accomplish it in Storyline 360.” Today, we’ll discuss three methods for temporarily locking interactions. Method
State changes are sometimes overlooked by many new users in Storyline, mainly because they are apprehensive about how they can be used. A question was asked in one of my recent courses about how one might get buttons or other items to disappear when they were clicked. A specific use case might be if you are using a button to start the motion path of another object, but you do not want the button to distract the learner or be “in the way” of the object that is moving, or
During Storyline training, we learn how to customize a course to ensure that learners view all the content on each slide. Depending on the situation and the type of content, there are a variety of strategies that can be used. One question that is often raised is, “How do I ensure my learners view all of the interactive content on a slide before moving on?” That’s a pretty popular question and David Anderson does a great job explaining how to do that here. However, sometimes the request is more specific.
Although not used as often, the “=NotAssignment” (also known as “toggle”) variable/trigger can be a great way to help you create engaging interactions for your learners! I was recently asked about a potential use for this trigger in class and, although there are other ways you could use it, I came up with the following example. We’re hopeful that this example and blog post not only accomplishes my goal of showing the use of the trigger, but also succeeds in wishing you happy holidays! One Button Versus Two A popular