This is a simple, customizable template that works in Storyline 2, 3, and 360. (The new Print Slide trigger included in Storyline 360 won't work in Storyline 2 or 3, because it requires the modern rather than the classic player.)
I tried using your template on my course, I publish to xAPI. Name and date correctly show up on certificate, but when I try to print, I get an error message.
<Error>
<Code>NoSuchKey</Code>
<Message>The specified key does not exist.</Message>
I'm assuming I need to tweak the javascript code, as i've added the certificate html file via resources, since I cannot simply add it to the published xAPI folder. Any ideas?
Hi Robert, I'm sorry you're running into a problem. I'm not a coder, so I might not be able to help. I'm not sure why you can't simply add the html file into the Storyline output folder, but that's the only way I know how to do it.
I tried to export it to Storyline 360 and then from there to a Rise project. The preview function gives me an error message and blocks the printing window. I think it is somewhere in the JavaScript. Me and ChatGTP are trying to solve the problem. But I'll let you know if I figure it out. But I'll follow this post, if anyone beats me to it :-)
Has anyone been successful with this certificate template, or a similar process, when publishing to Reach 360? I'm looking for a customizable certificate option beyond what is currently available through Reach 360.
7 Replies
This looks great, Tracy! 🤩 Thanks so much for sharing!
Thank you, Sarah!
I tried using your template on my course, I publish to xAPI. Name and date correctly show up on certificate, but when I try to print, I get an error message.
Hi Robert,
I'm sorry you're running into a problem. I'm not a coder, so I might not be able to help. I'm not sure why you can't simply add the html file into the Storyline output folder, but that's the only way I know how to do it.
I tried to export it to Storyline 360 and then from there to a Rise project. The preview function gives me an error message and blocks the printing window. I think it is somewhere in the JavaScript. Me and ChatGTP are trying to solve the problem. But I'll let you know if I figure it out. But I'll follow this post, if anyone beats me to it :-)
Thanks, Kasper, I'll be interested to read about it if you solve the issue!
Has anyone been successful with this certificate template, or a similar process, when publishing to Reach 360? I'm looking for a customizable certificate option beyond what is currently available through Reach 360.