Forum Discussion
Navigation in courses - User Specific
I have a software simulation module I am building. This module has sections that are only applicable for certain customers, in either a group A or a Group B. Each group will see almost the same thing, but there are certain pieces not applicable to one group.
What is my strategy for implementing navigation for one group of users that skips over certain sections and not the other?
19 Replies
I should also add that the pieces not applicable are in the same sections. So I have a section that is 50 slides long and there are parts within that group that aren't applicable to the other group
This post as a file that demos ways to provide branching paths: TIP: Let the user choose their path | Articulate - Community
Note: Storyline doesn't have a way to change the built-in Menu based on a chosen path. The post links to some solutions for that.
my boss has explained to me that she wants variables to show or hide information based on the role the user has. The software simulation has a large menu that is explained and then walked through and shows certain things by roles but she doesn't want duplicate slides for each learner. I am looking for any information on how to create something like this
That is exactly what the demo in the post I linked to shows how to do: navigate through the same set of slides but skipping some slides based on the chosen path.
I am going to take another look and try again and download the sample file you had sent, the last time it showed up as corrupted. I have a new work laptop and it has been issue after issue. Thanks for the guidance, Judy !
I don't have any trouble opening the file when I download it from the post. I suggest you try again. If it doesn't work, try again with a different browser.
As per Articulate guidance, be sure it's on your local drive. (Opening a .story file over a network can corrupt the file due to network lag.)
There's also a link to the published file in Review (https://360.articulate.com/review/content/f077476d-6c7d-4b83-a83d-4b1213a1ddee/review ). The slides explain the programming, so viewing that published version might help.
sarahrydgren-ab : I'll add one more note of encouragement.
You say the software has sections, and the different groups (A or B) sometimes need to see different sections. Even with lots of slides, the storyboarding might be easier than you think.
A "next" trigger with conditions is only needed on a slide that both groups see, but where Group A needs to jump to a different slide than Group B.
On slides seen by only one group, the "next" trigger doesn't need conditions. It just needs to jump to whatever slide is "next" for that group.
For easier programming, you could put each section into its own scene. All of those slides would use the standard "jump to next slide" trigger—except for the last slide in the section/scene. That is where you might need a trigger with conditions to jump to the appropriate scene based on the value of the tracking variable. But if both groups need to see the next section/scene, you only need a simple "jump to scene __" trigger.
Or, if you prefer keeping everything in one scene, remember that a "next" trigger with conditions is only needed on any slide that is seen by more than one group and that is followed by different slides based on the group (that is, one group skips the next section). And a "next" trigger that indicates a specific slide is needed on any slide in which the group who sees that slide needs to skip the next section in the overall sequence.
I honestly think my biggest issue was extreme overthinking. I do have a question, when creating paths by using variables and triggers, I had used buttons, not radio buttons to signal the choice and set the ROLE variable but it doesn't seem to translate once there is a branch. Does the clickable item NEED to be a radio button?
The way I look at it, any object can be turned into a button by adding a trigger that runs when the object is clicked. In other words, it doesn't matter what the user clicks to choose their role. It only matters that clicking the object adjusts the variable to the proper role.
However, if the buttons have a Selected state, they should be put into a button set. A button set acts like the radio buttons in a multiple-choice question. Only one item can be selected at a time. Selecting one automatically deselects the others. That's needed so it's obvious which button is selected. Here's more info:
- Storyline 360: Working with Button Sets | Articulate - Community
- PRIMER: Take advantage of built-in states | Articulate - Community
I mentioned in a previous reply that inserting the variable reference isn't required (that is, you don't need to show the variable's value on the slides). But, as I also said, it can be helpful to display the variable reference when you're programming. That lets you see if the variable is changing as expected.
You said "it doesn't seem to translate once there is a branch." It's possible that the triggers aren't adjusting the variable as expected. Or (and this is an easy mistake to make with text-variable values), the condition in the trigger for branching has the wrong value entered.
It's difficult to troubleshoot without seeing the .story file, so I'll repeat something else from a previous reply:
I suggest you carefully review all the previous replies and links, as well as the demo file. Then try programming the first part of your course, or even just a simplified, mock-up project. When programming and testing that, pay extra attention to ensure every trigger refers to the appropriate variable value and slide.
Then, if you have additional issues/questions, start a new discussion that includes a copy of your .story file and details about what isn't working as expected.
Thanks so much, I am excited to finally get this figured out and appreciate the assistance!
