Storyline Suspend Data Compression

I do have a bit of experience dealing with customers using SAP Success Factors.  It has definitely been one of the more pain-in-the-derrière LMS systems.   And yes, SuccessFactors seems to be fixed in time on SCORM 1.2 (and doesn't even support recording interaction data).   Anyway, this fix should still help and work fine. But like you, and with my previous SuccessFactors experiences, I would be hesitant to give a 100% guarantee, at least without someone first testing your course on your client's specific version of SuccessFactors.   Though, I do know that by using base64 encoding, the suspend_data itself should be fine with SuccessFactors as long as it's not truncated.  What would cause me reservation is just the broad number of issues I've encountered with SuccessFactors.

As to whether the suspend_data actually gets truncated or not, that should depend solely on whether your course creates more than 4096 bytes of compressed data.  What we usually do is test our courses on cloud.scorm through to the last slide and then exit (causing a suspend).  We then look at the registration data on cloud.scorm and examine the size of the suspend_data (typically, you can just copy the result into a web-based byte/string counter and see how long it is).  If it's close to 4096, then we have concerns.  If it's smaller by at least a 10% margin, then we feel more confident that everything will be fine.  Otherwise, we have to figure out how to trim out some of the items that cause saved state to be larger (typically we pair down the number of interactions).

I hope that helps!   And good luck!