Forum Discussion
Advanced Branching
Part of the problem relates to having two competing variables for customer or associate. Storyline will fire the first trigger in the list that matches the set values. If you previously followed the customer path, then the RoleCustomer is set to True. Even if you subsequently select the Associate path, RoleCustomer is still True, and since the triggers to jump to a home page place the customer trigger first, you always return to that page (Slide 2.23).
A fix could be to explicitly set and unset the Role variables. So, on Slide 1.6, add an extra trigger before each current Set Role trigger. Before setting the RoleCustomer to True, set RoleEcolab to False, and vice versa for the other set of triggers. This way, only one Role variable is true at the same time.
Alternatively, set the variables to False at the end of each training section to clear them, or if there are just two roles, you could just use a T/F isRoleCustomer variable to differentiate the roles. Just explicitly specifing both on Slide 1.6 is the easiest though.
Just watch out for any other areas in your project that may set conflicting variables that you later want to use for conditional decisions.
Part of the problem relates to having two competing variables for customer or associate. Storyline will fire the first trigger in the list that matches the set values. If you previously followed the customer path, then the RoleCustomer is set to True. Even if you subsequently select the Associate path, RoleCustomer is still True, and since the triggers to jump to a home page place the customer trigger first, you always return to that page (Slide 2.23).
A fix could be to explicitly set and unset the Role variables. So, on Slide 1.6, add an extra trigger before each current Set Role trigger. Before setting the RoleCustomer to True, set RoleEcolab to False, and vice versa for the other set of triggers. This way, only one Role variable is true at the same time.
Alternatively, set the variables to False at the end of each training section to clear them, or if there are just two roles, you could just use a T/F isRoleCustomer variable to differentiate the roles. Just explicitly specifing both on Slide 1.6 is the easiest though.
Just watch out for any other areas in your project that may set conflicting variables that you later want to use for conditional decisions.
Nathan_Hilliard​ thank you, this worked!