Forum Discussion
Unable to generate review link from SCROM
Hi MurariVyas!
It sounds like you're trying to manually upload a SCORM package to Review 360!
While Review 360 allows you to manually upload videos and Storyline 360 courses, it does not support direct uploads of SCORM packages. Instead, we recommend publishing directly from an Articulate 360 authoring app to Review 360. If a firewall issue is preventing you from publishing directly from Storyline to Review, you have the option to publish the Storyline course locally then manually upload the local file to Review.
However, Rise 360 currently does not support manually uploading courses to Review 360.
Please let me know if you need anything else!
Hi Steve;
What then is the zipped file that is being spoken about here?
Zipped story file is SCROM only what else is being referred to here.
Unable to understand please assist.
Hi MurariVyas!
Thanks for following up!
The line you've referenced from our guide, about a zipped file being generated, refers to the published output folder that Storyline creates for different publishing formats (like LMS/SCORM, Web, or Review 360). Even though it is technically a "zipped file of your Storyline course", it is not in the format Review 360 expects and requires to upload the item successfully. If you publish for LMS, you’ll receive a zipped SCORM package, which includes files like imsmanifest.xml. This file is only meant for upload to an LMS, and is not compatible with Review 360.
A simple way to think about it is all SCORM packages are zipped files, but not all zipped files are SCORM packages.
Please let me know if you need anything else!
Would have been really helpful if this is made much clearer with more screenshots for clarity cuz as of now it was giving an impression that when we publish the storyfiles we get a generic folder output along with ability to zip it as a SCROM package.
A more detailed guide would be much appreciated, thanks.
Hi MurariVyas!
Thank you for providing the feedback. I'm happy to share your request with our documentation team!
The article we're discussing does not mention SCORM files intentionally, as it's only meant to outline the process for publishing a Storyline file locally. So it can then be manually uploaded to Review 360. Publishing directly from Storyline 360 to Review 360 is the more streamlined way of uploading your content to the Review platform.
Alternatively, if your goal is to create a Storyline SCORM package for LMS, publishing directly from Storyline to LMS is the suggested method.