Previous button trigger

Hi Andre, 

Thanks for the detailed explanation here and providing some scenarios for when you've encountered this. Since both the previous and next behavior are currently set up as is, and by design - it would need to be something submitted as a feature request.  I do not claim to know the thoughts or ideas behind our team who created Storyline, but I suspect the "next" button does not function as a typical browser button does, based on the fact that this is for the user to be able to advance within the course - whereas on a browser, you'd need to click on something within the screen to advance and then if you used the previous button to go back one screen the next button would now be active. Storyline allows for the course to be set up with the default "jump to next slide" in the sequence or with a trigger to jump to a particular slide, or even remove all the player navigation and create your own navigation - it allows for some flexibility. But as you mentioned, if you set up a custom "previous" behavior - you'll likely need to set that up for each slide. 

The suspend data in SCORM 1.2 is limited, but Storyline does compress suspend data to help with the overall amount of data that is reported while still allowing the user to pick up where they left off to help prevent you from exceeding the data limit. Again, in your scenario (ignoring the loop for a minute) you'd want to have the previous clicks remember, so that the user wasn't prompted with the C slide again after already viewing it. Currently there is not a way to change what suspend data is reported and tracked - although I have seen a few other threads where users set up submission of such data using Javascript or similar.  If as you shared here, you'd like to see a more customized approach to what is sent and how often, that would also have to be a feature request at this time. 

If there is anything else we can assist with, please feel free to let us know.