Yes and no, and I'm trying to remember the whole issue, which is embarrassing since I first reported it during the beta.
I hope I'm remembering this right but if course resume is not turned on, variables are not sent to the LMS. Some of us wanted this ability regardless of the resume setting.
The variables are stored in the resume date and will be aviaiable as long as the user resumes or you force resume.We did suggest in the beta forum that it would be nice for use to be able to choose persistant variables and I think Gerry, Steve and I put in feature requests and got an ear pulling from Magnus.
He thought it was a good idea but there was no chance for version1 hopefully sometime soon.
Yes, by default the variables are stored in suspend data. When restoring from a previous session, the variables will be loaded from the LMS into your story. There are three options for that: always restore, never restore, and prompt. If you want to be sure that the variables are restored when the session is relaunched, it's best to choose always restore.
The other thing you'll want to watch out for is the number of variables and the scope of your course. If your LMS only supports 4K characters in suspend data (SCORM 1.2 lower limit for this field) you'll eat that up quickly with long variable names and large contents. Not such a big issue with an LMS that doesn't constrain the size of the field. Some vendors strictly interpret the lowest size as "the size". I've seen tale of folks running out of suspend data space.
Storyline stores variables in suspend data when loaded to an LMS. It will store and restore the variable values set in triggers and the states of objects on a slide when the slide is set to restore. It's been this way since version 1.0.
9 Replies
Yes and no, and I'm trying to remember the whole issue, which is embarrassing since I first reported it during the beta.
I hope I'm remembering this right but if course resume is not turned on, variables are not sent to the LMS. Some of us wanted this ability regardless of the resume setting.
Phil or Steve--do you remember the details?
The variables are stored in the resume date and will be aviaiable as long as the user resumes or you force resume.We did suggest in the beta forum that it would be nice for use to be able to choose persistant variables and I think Gerry, Steve and I put in feature requests and got an ear pulling from Magnus.
He thought it was a good idea but there was no chance for version1 hopefully sometime soon.
Yes, by default the variables are stored in suspend data. When restoring from a previous session, the variables will be loaded from the LMS into your story. There are three options for that: always restore, never restore, and prompt. If you want to be sure that the variables are restored when the session is relaunched, it's best to choose always restore.
The other thing you'll want to watch out for is the number of variables and the scope of your course. If your LMS only supports 4K characters in suspend data (SCORM 1.2 lower limit for this field) you'll eat that up quickly with long variable names and large contents. Not such a big issue with an LMS that doesn't constrain the size of the field. Some vendors strictly interpret the lowest size as "the size". I've seen tale of folks running out of suspend data space.
Thanks, Phil.
BTW, Magnus was always nice to me . . .
Do we have persistent variables yet?
Storyline stores variables in suspend data when loaded to an LMS. It will store and restore the variable values set in triggers and the states of objects on a slide when the slide is set to restore. It's been this way since version 1.0.
Thank you! What do you mean when a slide is 'set to restore'? I do not see that in slide properties. Or do you mean when 'Resume' is set to 'always'?
Yep.
This discussion is closed. You can start a new discussion or contact Articulate Support.