Forum Discussion
Advanced Branching
- 2 months ago
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.
Hello,
I have a guess as to what is happening. You might wish to explore this idea.
If a learner clicks Customer, then you would be using a variable, "RoleCustomer" to be changed to True. With this variable set as True, then the following experience would be triggered to be customer-oriented. However, upon returning to the point where the Associate path is chosen/used, is there anything to turn off the "RoleCustomer" variable to "False"? If not, then perhaps the project is continuing to send the user back to Customer slides because the "RoleCustomer" variable is still True.
It seems to me that you can send learners to 2.1 on both the Customer Path and the Associate Path. However, at the last slide in the scene of 2.23, your triggers to send the learner back to either the Customer or Associate home screen are dependent upon whether or not the "RoleCustomer" or "RoleEcolab" variables are true. Wouldn't it be possible to visit 2.23 as a Customer, then visit 2.23 as an Associate, and then be sent back to 1.7 Customer Home because the "RoleCustomer" variable was initially set to True before the first visit to 2.23, and then never turned to False on the second visit to 2.23?
If this solves your problem, please mark it as Solved. Otherwise, feel free to ask a follow-up question or post an additional comment.
Related Content
- 8 months ago
- 5 months ago