LMS commit exception handling

Hi Zack,

Have you seen t he information here? 

Hi Ashley,

Yes, it doesn't fix the problem.

Problem is JavaScript popup are easily ignore or blocked.

Only fool proofing the process of scorm lms commit is to add conditional slide before displaying the user completions/score/result screen. This additional slides should allow learner to resubmit the lms commit request in case of failure due to any reason. 

I hope this helps.

Thanks Zack and if you're able to use that method and have success I hope you'll be able to continue using it as you go forward.

@Ashley ... Actually am hoping some kind of help or assistance for Articulate or Community. 

Hi Zack,

Sorry for my misunderstanding - the documentation I provided is all that we have within Articulate currently so otherwise I'd have to defer to the community for more assistance. 

Hi Ashley,

Had raised feature request few days ago. It will be great help if you can just check status with the team.

-Thanks.

Hey there, Zack.  Thanks for following up!  We don't have any updates at this time, but if a feature is added in an updated version of Storyline, we cover that in the release notes, support cases and in relevant community discussions.  

Just to share for you and others who are curious about our feature request process:

1) First, we see if the request is currently possible, and we let you know if there's a way to achieve your goal. 

2) If the request isn't currently supported, we estimate the value it could bring to our products. 

3) If a request adds value, we submit it to our product development team for review. 

4) Our development team gauges the impact of the request. Will it benefit many of our customers, or does it meet a niche need? 

5) If the request is approved, we add it to the development pipeline where it gets designed, developed, and tested. 

6) When the feature is ready, we release it and announce its arrival. 

Thanks again!

Appreciate your response. Went through the outlined process and feel my request seems to be good addition.

Quick Feedback, process can be more transparent. You may check great practise followed around. To name relevant co... Jetbrains > https://youtrack.jetbrains.com/issues

Thanks Zack for sharing the practice of another feature request process - having a public view into our process and roadmap is something that our team has discussed and we continue to look into ideas or the way in which to make this a viable set up for Articulate. 

I had the same issue, and our thought was that Storyline sends the commit/finish on window close (but have been unable to verify), and the data was unable to be sent quickly enough. There was varying success, so sometimes it would go through, sometimes not. But the solution for me was to, on the last slide, at 1 second, execute javascript:

// set score, complete, whatever you need, and then:

LMSCommit("");

(needed to include the empty string)

Thanks for popping in here to share your solution, Jacqui! Really appreciate it ☺️