Storyline Suspend_data decipher

Its not really a feature request that is needed for this. The LMS suspend data is already a part of SL, it already reads and writes the date to the LMS in a compressed format. We just need to know how to uncompress the string edit the data and recompress before submiting the data to the lms.

Hi Christian,

It is a feature request to uncompress it or make the current output human readable. It's by design that the data is compressed to allow for more data to be captured. 

What elements are you looking to edit? That would be helpful information to include in a feature request! 

Just looking to update the suspend_data manually to change the furthest frame value to the furthest frame the user has EVER reached. Not just the furthest frame they got to in the most recent launch of the module.

Thanks Christian - I can see how that'd be helpful and I appreciate you sharing here. You can also always share Feature requests here too.  If you’re wondering what happens when you submit a feature request, here’s our process.

We've had some issues with articulate courses freezing and content not loading, leaving the users on a blank page. As you can see here:

https://community.articulate.com/discussions/articulate-storyline/articulate-storyline-579b4554-0b22-4e80-b7c7-2957f6521882

We havent been able to figure out what the problem is and meanwhile, users are getting stuck on a slide. We would be able to redirect them to the slide they viewed if suspend data was readable.

Thanks Daniela and I see you're working in that other discussion with Leslie and Eloisa as a part of a Support case. It's another good use case for why you'd like to be able to edit the suspend data too so I appreciate you sharing here. 

I've spent days trying to figure out why we're getting javascript errors when participants resume courses on a client's proprietary LMS. The fact we cannot read suspend data makes troubleshooting nearly impossible. If you want high-end developers using your products, you need to give us the tools to troubleshoot problems. Our firm has decided to migrate this client's project to Captivate solely due to this issue.

Hello Doron!

Sorry to hear that you spent days experiencing an error before reaching out. I'm sure that is frustrating.

We do have an LMS Debug Log to assist users in troubleshooting and typically advise testing the content in SCORM Cloud as well to see if the issue is able to replicated in a standard environment.

If you find that the issue is within our software or have additional questions, you are always welcome to work directly with our support engineers as well.

Just stumbled upon this conversation in search of the real point of the debug log if you can't decipher the data string(s.)  I am in that situation now.  I am looking at both debug and LMS course transaction reports from a sample course published in: SCORM 1.2, 2004 - 3rd and 4th ed.

I want to see the data interaction between the course/player and the LMS to see what is the most efficient platform.  I haven't even worried about xAPI yet.  I've been able to parse the debug and report data, but not make sense of it without the "decoder-ring."  

In reference to David Keeling's request I believe the standard for SCORM 2004 will do just that.
In the parameters it has one for course tracking and completion and one for tracking quiz completion.

SCORM1.2's (lesson_Status) was split into 2 parameters in SCORM2004; ‘completion_status’ (completed/incomplete) for the course and ‘success_status’ (passed/failed) for the quiz. Now whether SL sends both calls is another matter which is why I am attempting to decipher the debug and lms data reports.  Is there any way to read or decipher the debug log? 

Hi Paul, 

Our  LMS debug mode will let you see the data being passed from Storyline to your LMS, but the suspend data/bookmarking elements are compressed and not human readable. The other data should be there for you and if you're having difficulty deciphering it our Support team is happy to help! 

You'll want to upload a copy of your .story file, the debug log and a link to the course if your LMS (in you're able). They'll take a look at testing it and be in touch with you via email as soon as they can!