An employee left the company and we cannot locate the source file (.story) for an e-learning. We have access to their Articulate account and can see the file we are looking for in the Review 360 section. We can launch the review and complete it. Is there any way to capture the .story file from the review?
Unfortunately, you can'tget a .story file from a published version of the course. If you can't find the source .story file, you'll have to re-create it.
FYI: Articulate has a new feature (in beta) that allows for uploading the .story file when publishing to Review 360, which would provide a back-up copy. Alas, that doesn't help you now, but it's useful to know for future reference.
Those publishing to a Review 360 team folder will be able to retrieve a file even if the person who published the original file leaves the team. Here's that part of the article:
Obviously, it's important to ensure that everyone on a team includes the backup file when publishing, and that they publish to a Review 360 team folder.
I'd suggest having all files stored in a shared location on the company's intranet, too—especially since the back-up function is only in beta. (Also check as needed to ensure everyone is backing up files as they should.)
3 Replies
Unfortunately, you can't get a .story file from a published version of the course. If you can't find the source .story file, you'll have to re-create it.
FYI: Articulate has a new feature (in beta) that allows for uploading the .story file when publishing to Review 360, which would provide a back-up copy. Alas, that doesn't help you now, but it's useful to know for future reference.
Thank you for the information. I will using the new feature to have access to an additional back-up.
FYI: Here's the article about the back-up feature:
New in Storyline 360: Cloud Backup (Beta) - Articulate Storyline Discussions - E-Learning Heroes
Those publishing to a Review 360 team folder will be able to retrieve a file even if the person who published the original file leaves the team. Here's that part of the article:
Obviously, it's important to ensure that everyone on a team includes the backup file when publishing, and that they publish to a Review 360 team folder.
I'd suggest having all files stored in a shared location on the company's intranet, too—especially since the back-up function is only in beta. (Also check as needed to ensure everyone is backing up files as they should.)