Hi there. As the title says, I was wondering if there was any way to set an expiry date for published content, which would basically stop users from being able to view the content after a specific date? I've used this feature in KnowledgePresenter before but can't find such a thing anywhere in Storyline. It would be very handy, as we are basically looking to put our course on disc to send out to people to trial them, but we don't want them having access to our courses beyond the trial period. Thanks again for any support on this.

I think I found somethint that might work using Java Script Create a trigger that runs this script when the first page timeline starts: var currentDate = new Date() var day = currentDate.getDate() var month = currentDate.getMonth() + 1 var year = currentDate.getFullYear()player.SetVar("day1", day);player.SetVar("month1", month);player.SetVar("year1", year); This sets numeric variables in Storyline for day, month and year from your computer. I created numeric varaibles, day1, month1, and year1 initially set to zero Then I created a trigger that would show a layer when the timeline starts if: day1 is greater than a specific number, in my example, 7 and month1 is greater than or equal to a specific number, in my example, 2 and year1 is greater than or equal to a specific number, in my example, 2013 That layer displays text that the content expired and has a close course button. I disabled the next button and added a continue button on the first page. If the Expired layer is visible, I prevented users from clicking items on the base layer. I included the variables on the first page for testing, but they need not display. Here is the file, you must publish to test. To test the expiration, set your computer for a date in the future beyond your expiration date.

Now that I think about the logic of the trigger, you may need to create 3 separate triggers to launch the expired layer. The first trigger is if year1 is greater than or equal to a specific year show the expired layer. So if the course expires in 2014, that would be the year. The next trigger shows the expired layer if the month1 and year1 has been passed. This covers a scenario of a course expiring within a calendar year, for example, June 2013. The final variable is as in my previous post. This covers a course expiring mid month within a calendar year. This is a 3 point date validation: The year is less than the expiration date, The month and year are less than the expiration date, and The day, month, and year are less than the expiration date. Any expiration will show the expired layer.

Jim, SCORM Cloud has a rather unique pricing strategy that I think you might have misunderstood. Check out: http://scorm.com/scorm-solved/scorm-cloud-pricing/scorm-cloud-pricing-all-of-the-details/ "Do I have to keep paying for registrations each month once I have created them? Great news! We want to be awesome to you, so you only pay for the registration when it was created. After that, learners can access the course as often and as long as they like (or you want them to) without any additional registration fees." This means that you pay only for the registrations "purchased" that month. They even send you an email right before you are billed, I believe so that you can go into your account and change your plan accordingly if you have had a lot of registrations that month. This easily gets the cost per registration down to $0.10 each for large numbers. You should at least set up a trial account to check out their functionality, We've worked with Geoff at Rustici (SCORM Cloud) quite a bit and their guys are amazingly helpful. Oddly, they don't really seem to be in it to make money, just to be SCORM evangelists. They do sell an Enterprise product though, if you would like your own SCORM Cloud. Thanks, Mike

Hi Alyssa, We deliver content to clients to host on their LMS, so this feature would be extremely useful. Thanks for your reply.

I am happy to see that so many people are requesting this functionality to be in the software, but a little shocked that we are in the same place as the first request 6 years ago. We also sell SCORM packages in 1 and 3-year contracts and need a better way to ensure the files are disabled or expire so we aren't losing money.

Setting an expiry date for published content

LeslieMcKerchie
Staff
6 years ago
Thanks so much for chiming in to share that you would like to see this feature implemented as well, Kassie.

I've pulled together conversations in the forums as well as a few of the official feature requests that were filed so that we can better track this request.

I wanted to share some information about how we manage these feature requests as that may be helpful.
F0rt_Kn0xDiona
Community Member
6 years ago
Our clients require an expiration date on their courses. We were a Captivate shop and this feature is built into the Publish Settings. But we recently started using Storyline exclusively and are only now realizing that there is NO expiration date that can be set for published courses. We are hoping there will be an upgrade including this soon or a workaround that is compatible with multi-platforms and mobile media as well.
AnjaliPanakkat-
Community Member
6 years ago
Really need this expiration date on the published SCORM, as a feature in storyline.
GerryWasiluk
Community Member
6 years ago
Some LMS's provide this feature. For content in an LMS, this may often be the preferred option.

As for non-LMS content, it would be nice to have.
KaitieConrad
Community Member
6 years ago
Any updates on this feature?
KatieRiggio
Staff
5 years ago
Good morning, Kaitie!

A feature that would allow setting an expiration date for content is not on our immediate roadmap—as the hosting platform typically determines this—but we're still tracking all requests.

If plans change, you're in the right place to know more!
ISDImpact
Community Member
5 years ago
The above solution is great for Storyline, thank you for paving the way!

I was wondering if anyone has tried to set a SCORM expiration date for a Rise course?
CrystalKlarich
Community Member
5 years ago
I would also love to see expiration dates built into the software, as we sell our courses to people for use on their own LMSs. While it would be lovely to have everyone manage the expiration on their own LMS, it does not make practical business sense.

I was able to get Owen's code to work with a small tweak. I kept getting an infinite loop error and slides were taking forever to load with the code written as it is above. I added stop() at the very end of the javascript and it works perfectly now. The only other change I made was to add a 1 second delay for when the jump to the "expired" slide trigger happens, because I couldn't get the trigger priority to work for some reason. I didn't spend much time exploring that issue, as we actually preferred the look of it. It made the expiration effect a little more pronounced.

Thanks for the help!
- OwenHolt
  Super Hero
  5 years ago
  Glad you found it useful. 😎
  - AmyLeelo
    Community Member
    4 years ago
    Hi Owen - do you know you would hard code the variables as you mentioned above?
SerenaPill
Community Member
4 years ago
+1 for this to be included on the roadmap
OwenHolt
Super Hero
3 years ago
I can probably do that but will need additional info to fully scope and see if my idea on how to cap users will even be a viable option. Send me a LinkedIn connection request and we can arrange a zoom meeting through messaging there to discuss.