2-hr Navigation Restricted Course Finished in 10 Minutes
Nov 18, 2019
Hi Guys,
This is an interesting one, at least to me. I have a number of 2-4 hour regulatory courses made in sl 360. These are published to SCORM and sitting on an LMS and I have a number of learners taking the courses. All the courses have restricted navigation, meaning the Next button on the page is inactive until the page timer plays out. The Seekbar and Menu are also restricted so the learner cannot jump through the slide or to the next page until the current page has played out completely. Also, these courses are all published in the standard (customized) sl player. Nothing other than what is built into sl. The completion is based on number of slides viewed.
Yesterday, someone was able to complete 20 hours of courses in a day with extremely short times start and finish times recorded on the LMS. For example, an hour for a 3-hour course and two hours for a 4-hour course. These times vary for different courses, they aren't consistent. Also, this is for only 1-person and multiple courses. Other learners have normal times showing ie. two hours, 30 minutes for a 2-hour course, five hours for a 4-hour course, etc.
I suspect, rather groundlessly, someone either using an autoclicker or maybe editing the javascript to send the completion status or something else. Has anyone else faced a similar situation? Any ideas on what could have happened here?
13 Replies
I doubt they could edit the JS. If you use video, some browsers allow you to right-click and increase the playback speed.
No video, just images and text.
Hmm, then the only other thing I can think of is that the menu navigation is not restricted and they can jump around.
Menu is locked down and the seekbar is also restricted.
Hi Akhilesh,
Thanks for reaching out and letting us know that you're running into issues with your course restriction.
With your permission, I'd like you to share your project file with our support engineers to investigate what's happening. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.
They probably used keyboard navigation. Try taking a new instance of the course in your LMS and press the Tab key on your keyboard, which should show you the "area of focus" highlighed with a yellow outline. Keep pressing Tab until your area of focus is on the Next button, and then press Enter on the keyboard. I have seen that this is a way around locked navigation.
Thanks for your note. I tried this right now and still the same. Cant progress until the Next button becomes active. I tried the tabbing through multiple screens with the same results. It doesn't progress until the Next button becomes active.
Thanks Leslie, I'll sanitize and upload the file. As you would probably imagine, I need to be sure before of the how, before approaching the student about how they were able to do it.
Hi there, Akhilesh!
Great call to open a case with our team–I see that you and Christopher are already bouncing some ideas around this goal!
Thanks for continuing to reach out, and I'll follow the conversation as it progresses!
Greetings,
Was this resolved? In response to significant cheating (going through 60 minute lecture modules in a couple of minutes) I've rebuilt a university course using the same methodology in the initial description. I tried the Tab scenario but that didn't advance the student. Many thanks.
Hi Susan!
I see that you're working with my colleague, Jarlan, in a support case! We'll continue the conversation in your support case.
I'm putting the resolution here for anyone else interested in the compliance approach.
To address the same issue, our developers have come up with an update for Storyline 360 last Aug 18 (Build 3.43.22859.0) which should also be a fix.
Hello ase asa!
Our latest update for Storyline 3 includes bug fixes that were released in Storyline 360 update 43. Have you updated Storyline 3 to make sure you're using Build 3.11.23355.0?
Download the latest Storyline 3 update here.
If you are still running into this snag, you can connect with a Support Engineer to begin troubleshooting!