Is there any way to use a variable between storyline files? I have a course that consists of mulitple modules. Each module is a separate storyline file. I want the student to enter data (e.g. name) in the first module then use that data in other modules wihout having to re-enter the data in each module. Is this possible? If so, how?
No way to work that at the moment using built-in features. By nature of SCORM and the cookie mechanism variables use, each package is separate and isolated.
How are you deploying your courses? There might be a custom workaround you could apply to send values from a story file to an intermediary and load those values into another story location.
Not directly, unfortunately. Moodle uses SCORM to interact with content and the implementation is subject to the same spec restrictions. There are good reasons for this most of the time. You should be able to pull the user's name from the Moodle account using SCORM without the participant needing to enter it. Is there other data you want to pull into the story and have shared between?
4 Replies
Hey, Rich -
No way to work that at the moment using built-in features. By nature of SCORM and the cookie mechanism variables use, each package is separate and isolated.
How are you deploying your courses? There might be a custom workaround you could apply to send values from a story file to an intermediary and load those values into another story location.
That's what I thought. We're deploying on Moodle. Know any way to do it through Moodle?
Not directly, unfortunately. Moodle uses SCORM to interact with content and the implementation is subject to the same spec restrictions. There are good reasons for this most of the time. You should be able to pull the user's name from the Moodle account using SCORM without the participant needing to enter it. Is there other data you want to pull into the story and have shared between?
Thanks Steve! Yes, there is quite a bit of data we want to pull. Sounds like we'll have to find some other solution.
This discussion is closed. You can start a new discussion or contact Articulate Support.