I have a Flash file that sets and gets variables in Storyline. The issue that I am having is getting the variables to save and hold when the course is resumed. The only way I can get the variables to save is if the user navigates to another slide. Is there a way to have the variables save and hold without navigating away from the slide with the Flash file?
When you write vars in SL, or from a Flash file in your content area, SL will store the information in cache.
Cache, by nature, is static until a process is told to send it.
As an example, when you publish your SL project for TinCan, the cached information is sent to the LMS each time you click the Next button. The Next button calls the trigger process to send the data.
If you are sending data from the content area, you will need to use an equivalent type of process.
To do this, you can have your Flash data be processed using a JavaScript trigger to PUT the processed data.
5 Replies
Hi Mike:
When you write vars in SL, or from a Flash file in your content area, SL will store the information in cache.
Cache, by nature, is static until a process is told to send it.
As an example, when you publish your SL project for TinCan, the cached information is sent to the LMS each time you click the Next button. The Next button calls the trigger process to send the data.
If you are sending data from the content area, you will need to use an equivalent type of process.
To do this, you can have your Flash data be processed using a JavaScript trigger to PUT the processed data.
Hope this helps.
Best Regards,
Dennis Hall
Thank you Dennis for the suggestion. Do you have any samples of this type of script or know where I can find a tutorial?
Thanks
Mike
Mike,
Not sure if this would work for you, but another community member used a "saved slide" solution. It's a little more low-tech, but is something to consider. We did a write up on it here. http://www.articulate.com/blog/save-states-slide-upon-resume-storyline/
Mike
Thanks Mike. I think this might be a good solution.
Thanks for the update Mike S!
This discussion is closed. You can start a new discussion or contact Articulate Support.