I've been searching the posts on this topic for several days. I've tried several things that were recommended but I am still experiencing this issue.
I have a fairly large course with several "main menu" slides. This training requires the learner to "attest" to completing the course to get credit. I have a confirmation page that states "by clicking Next, you attest to..." The next button on this slide is set with the "complete the course" trigger, and takes you to the "Congratulation" page, where a custom "Exit" button is set with the "Exit course" trigger.
I've uploaded to our LMS several times using the "passed/incomplete" and the "Completed/Incomplete" settings, but the LMS still reports "In Progress".
5 Replies
The order of triggers may be important here. Does the trigger for "jump to next page" happen before or after the "complete course" trigger?
Alternately, move the "complete course" trigger on the "Congratulations" page, having it execute when the timeline starts. Any change?
Are you using the Classic player? What build are you on?
Hi, i have the same problems with my trigger. It worked well in the past, but if i save the file under a new name the trigger does not worked.
Any solutions?
Best chris
hi, the bug is fixed in the new update. I just installed it and the bug is fixed and the trigger are working fine.
https://articulate.com/de-DE/support/article/Articulate-Storyline-360-Version-History
best chris
This post was removed by the author
I appreciate the update and confirmation that the latest update was able to solve this issue for you as well, Christoph.
For anyone else following along:
We just released another update for Articulate 360 and included a few new features, enhancements, and fixes you'll see in the release notes.
The item you'll be interested in is:
Fixed: Course completion triggers stopped working in the classic player.
Just launch the Articulate 360 desktop app on your computer and click the Update button for Storyline 360. Details here.
Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.