If you want a learner to do multiple tasks on one slide, then a bespoke interaction can be a better route. On this slide, for example, the learner has to fill in a form with multiple parts.
The form has a section where the learner saudi arabia phone number list has to type something in as well as two different multiple-choice sections. It’s more realistic for the learner to have to fill all these parts of the form in at once – that’s what they’ll be doing in the real world – but Storyline’s freeform questions aren’t able to handle all these parts at once.
To create this type of complex scenario, triggers and variables. The first thing you’ll need to do is to lay out your assets on the slide. Again, go to the Insert tab and add visual and text content. You can add text entry functionality by going to the Input sub-menu and picking the text entry field from the dropdown menu.
Now everything is on the slide. By using Storyline’s inbuilt inputs we don’t have to do much programming. The text entry field can be filled in by the learner, and they can select any and all of the check boxes. We’re nearly done! The final thing to do is make the three check boxes in the “State of Waste” section part of a button set. This is because we only want the learner to be able to select one of these check boxes, unlike the “Hazardous Properties” section where they can select all that apply.
To create a button set, you just select all the objects that you want to be part of the set, right click and select Button Set from the menu. Then assign them a button set: we’d recommend renaming this to something descriptive e.g., “Waste Form”. This is a quick and simple way of making it so that the learner can only pick from one of the available options on your slide.
All the functionality is now working on this slide, but we need to be able to capture whether the learner has filled in the form correctly so that we can give them meaningful feedback on their assessment performance. So, how do we do this?
Tracking and summary feedback
In this example, we need variables to track inputs and present feedback. This is because the feedback is generated on a separate slide from the interactions we’ve built above. Unlike object states, variables exist across an entire Storyline project. They’re a great way of tracking a learner’s progress across a complex scenario-based assessment, as you can use triggers to adapt variables based on learners’ actions across a sequence of slides.