The solution requires two parts: a) Storyline code and b) LMS support.
For (a) you would need to define a project numeric variable in SL that holds a value. Let's call the variable "Role". Every slide would need a trigger on timeline start that looks at the value of Role. If Role > X, go somewhere else...
Possible, but lots of work
Point (b) is more critical. does your LMS support passing the user's role, or custom variable. Ninety percent chance the answer is no, so things are stopped. If possible, you'll need to add code in SL to read the variable from the LMS launcher and set Role accordingly.
3 Replies
The solution requires two parts: a) Storyline code and b) LMS support.
For (a) you would need to define a project numeric variable in SL that holds a value. Let's call the variable "Role". Every slide would need a trigger on timeline start that looks at the value of Role. If Role > X, go somewhere else...
Possible, but lots of work
Point (b) is more critical. does your LMS support passing the user's role, or custom variable. Ninety percent chance the answer is no, so things are stopped. If possible, you'll need to add code in SL to read the variable from the LMS launcher and set Role accordingly.
Best of luck. Possible, but not trivial.
Thank you very much Brian...! but it is critical...
Once you get the id (by whatever means) here is a sample of how it can work.
This discussion is closed. You can start a new discussion or contact Articulate Support.