no idea whether this is actually technically doable but is it possible to integrate a certain kind of "self destruction" meachanism into SCOM file so that it de-activates itself after a programmed time?
Reason I'm asking is, that whenever we sell to a customer who is running their own LMS we simply need to trust that they don't use our course longer than agreed upon.
Not that we don't trust all of our clients, but hey - last time I checked my occupation it didn't say "Good Samaritan" but Businesman ;-)
I wanted to give this a try to I made a demo that seems to work. It is attached.
In the variables in the storyline file is one called expdate. It is in the format yyyymdd. You would set your expiry date with this and then the file will check whenever it is run. If you put that into rise you can put a continue block below it that is tied to completion of the block above. If it senses expiry, it will not allow you to complete, thus blocking you from the content. This assume a couple of things. You need to have locked navigation for one. Second, this will only work if it is run. If they have gone past the first screen, then they will not run this check and it will not block them.
Here is a Rise demo with the expiry date already past.
Hi TIm, thanks a lot! I've taken a closer look and wonder, how exactly you did the programming of this variables? Couldn't find anything when looking at the triggers. or did you do that in the Java Script?
Matthew - I approached SCORM CLOUD to answer some more questions that arose while thinking through their service offer of their dispatch solution. Mainly I'm worried about endless discussions with customers IT department for allowing communication between SCORM CLOUD and the customers LMS.
I know IT folks well and assuem this coulkd be a show stopper when talkign about openign ports in firewalls for allowing a two way communicaiton.
Any experiences someone? If someone is interested, I'll gladly share what SCORM CLOUD offers as explanations.
3 Replies
Matthias;
I wanted to give this a try to I made a demo that seems to work. It is attached.
In the variables in the storyline file is one called expdate. It is in the format yyyymdd. You would set your expiry date with this and then the file will check whenever it is run. If you put that into rise you can put a continue block below it that is tied to completion of the block above. If it senses expiry, it will not allow you to complete, thus blocking you from the content. This assume a couple of things. You need to have locked navigation for one. Second, this will only work if it is run. If they have gone past the first screen, then they will not run this check and it will not block them.
Here is a Rise demo with the expiry date already past.
https://rise.articulate.com/share/X-_NV63EKRW08mhmEMuMdG3MW8p2yJyj
Let me know if this makes sense.
Tim
Matthias;
This check is on the slide master so if it is a Storyline SCORM and not a block in Rise it will check every page they open.
Tim
Hi TIm, thanks a lot! I've taken a closer look and wonder, how exactly you did the programming of this variables? Couldn't find anything when looking at the triggers. or did you do that in the Java Script?
Matthew - I approached SCORM CLOUD to answer some more questions that arose while thinking through their service offer of their dispatch solution. Mainly I'm worried about endless discussions with customers IT department for allowing communication between SCORM CLOUD and the customers LMS.
I know IT folks well and assuem this coulkd be a show stopper when talkign about openign ports in firewalls for allowing a two way communicaiton.
Any experiences someone? If someone is interested, I'll gladly share what SCORM CLOUD offers as explanations.
This discussion is closed. You can start a new discussion or contact Articulate Support.