Mulitple Branching in one course how?

I am trying to find how to create a branching course.

This is what I have so far, the user comes in and they see a couple of slides and then at the end of that intro content, they need to choose their respective bucket/role.

This is where there will be 4 or 5 roles to choose, each will have specific content targeted to the respective role. and at the end all will be presented with one final assessment.

Now one of the roles will see the intro content and when they select their role they will get to the assessment. However, what if a user from another role selects that role, is there is way to stop them who by mistake or knowingly choose another role.

The client doesn't want anyone to skip their content if they choose the role which just has the assessment.

How to over come this complex navigation.

9 Replies
David Schwartz

Is it possible for you to ask the users to select their roles near the beginning of the module, before the intro slides, and capture that into a variable?  You could then branch according to the value of the variable.

In that way, if I understand the situation correctly, there would be no obvious menu for the users to chose their branch. 

I don't see how you could prevent a user from accidentally or intentionally selecting the wrong role, although maybe asking the user to confirm their choice might help.


tin C

David and Walt, I think I can have the users select their role at the beginning of the course and then do the branching, So are you saying if I do this, I cant show the menu right?

Walt I looked at your file and understand the concept, but don't know how to recreate it. Also what is the point of the password, once they select their role do they need to validate it again by entering the password? Sorry I don't understand this part.

David Schwartz


The idea here is that once a user selects his/her role, there is no need for the menu, since you will know which way to branch them. That should make it less likely for people to try to take the shortest route through the module, which seemed to be the issue that concerned you.

I can't speak for Walt, but assume he used the password as a way to allow you to better insure that people choose their correct roles. Of course if they know the code for another role, they can use it, but it gives a bit more security in preventing people from mistakenly or intentionally choosing the incorrect path.




Walt Hamilton

David is right about the password. I created that for someone who wanted to prevent the user from mistakenly or deliberately choosing the wrong path. In real life, the password wouldn't be listed on the slide, but would be known to the correct people.

They also wanted a very complex path. If it is too complex for you, you could get the user to choose a role, which assigns them a variable. Then if there are no slides that different roles have in common, at the very beginning, each user will be sent to their own scene, and follow a path through that scene.

This was set up for someone that wanted some unique slides and some slides in common. 

You CAN create it. Once a user chooses their role, assign a value to the main variable (in this case, I named it User). When it comes time to advance to another slide, build a trigger for each available path, and jump to the next slide in the path, depending on the value of that variable. Cows go to the next slide on the cow path, horses to the next slide on the horse path, etc. Sometimes the next slide is the same for two different paths, and sometimes not. Look at slide 1.28. It illustrates all the triggers and branching, and summarizes the logic needed.

In reference to the menu, If you show the built-in menu, every user can see it and use it to jump to any slide. The answer is not to show it, and if you want a menu, create a custom menu that is personalized to each role.