Storyline Suspend_data decipher

Ashley Terwilliger-Pollard
Staff

almost 7 years ago06/21/17 at 5:40 pm (UTC)

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.

Doron Brenner

over 6 years ago08/09/17 at 7:17 pm (UTC)

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.

Leslie McKerchie
Staff

over 6 years ago08/10/17 at 6:30 pm (UTC)

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.

Paul Zamora

almost 6 years ago06/06/18 at 10:24 pm (UTC)

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?

Ashley Terwilliger-Pollard
Staff

almost 6 years ago06/07/18 at 1:14 pm (UTC)

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!

James Jordan

almost 6 years ago06/28/18 at 8:01 pm (UTC)

I've figured out a way for you to somewhat decipher the encrypted suspend data, but you would need to have the Storyline file in order for it to be useful. Below is an example of a course we published on our SumTotal LMS. It has six modules with four assessments and a custom results slide that checks for passing in each of the modules. I've broken up the suspend data so it's easier to read with labels showing what each value means.

This is probably session information, but I haven't figured it out yet.

3JG1~2M2P190H0O0k0f0p0h0G0b0X0j0o0m0l002T1q0i0N1K1e0Q1D0Z1E0V0n2h2B0r0W032p2P0N0W1I070Z0w042R1O1j2X1U18012k2s0K0U0l2g0_1c0L1m2t0F0C062x0Q0v0n0R0Y0y0L0V1u022z0_0M1J1S172$1Y1d0A0a01060a2~2Jk~2Fk1001i16~2uk

This starts the slide capturing. It's always at this point after the initial data above. I matched these values with the slides in the .story file to make sure the number was correct.
01011 - Module 1 Slide 1
01111 - Module 1 Slide 2
01211 - Module 1 Slide 2 (Main Menu)

01012 - Module 2 Slide 1
01112 - Module 2 Slide 2
01212 - Module 2 Slide 3
01312 - Module 2 Slide 4
01412 - Module 2 Slide 5
01512 - Module 2 Slide 6
01a12 - Module 2 Slide 7
01512 - Module 2 Slide 6
01612 - Module 2 Slide 8
01512 - Module 2 Slide 6
01712 - Module 2 Slide 9
01512 - Module 2 Slide 6
01812 - Module 2 Slide 10
01512 - Module 2 Slide 6
01912 - Module 2 Slide 11
01b12 - Module 2 Slide 12
01c12 - Module 2 Slide 13