Integrated Review 360 Comments and Project Identifiers

Aug 01, 2023

Thank you for all the great feedback on integrated comments. Please keep them coming!

Many of you raised concerns about existing comments not displaying. We'll consider all your thoughts as we plan the next phase of this feature. In the meantime, I'd love to provide more context on what you're experiencing:

Every Storyline project has an identifier, a unique string of characters assigned by Storyline that LMSs and LRSs use to identify your course. When you create a project, Storyline generates its unique identifier. If you copy and paste the project file in File Explorer, the identifier stays the same. If you save the project as a new file in Storyline, the identifier changes on the assumption that this is a new course. To keep the original identifier when saving your project as a new file, change the value of the identifier in the Project Info window (shown below). Note that if you change the identifier, the course will no longer be associated with any previously published Reach 360 courses or Review 360 items.

Project Info

When you publish a project to Review 360, the identifier stays with the Review 360 item. This value tells Storyline when you're updating an existing content item in Review 360, and it's what Storyline uses to retrieve comments on a course. 

All this might result in some interesting scenarios, some of which were noted in the feedback we collected:

  • The Comments panel doesn't display after publishing a course to Review 360.
    In this case, the course identifier likely isn't associated with any Review 360 items. This could happen when saving a project as a new file after it was published to Review 360—or maybe before, in which course A was published while course B was open.
  • The Comments panel displays, but it doesn't show comments from the published Review 360 item.
    This could happen when publishing different Review 360 items. For example, you publish a course to Review 360 item 1 and Review 360 item 2. Comments display for Review 360 item 1, but we show comments for the most recently published review item (Review 360 item 2). This can happen when publishing a course to Review 360 for different audiences.
  • Comments from a different project display.
    In this case, the course identifier is the same as the one for another course published to Review 360. This happens when both courses are from the same original project or project template via copy/pasting the course in File Explorer. It's also possible that the author manually set the identifier, then saved the project as a new file.

Hope that provides some context and thanks again for sharing your thoughts. Let me know if you have any other questions!

4 Replies
Rock Hymas

Hi, everyone. We hope you’re enjoying in-app comments!

I’d like to call out a change in how we control access to integrated comments. Linked Review 360 items and their comments are now retained when you save your Storyline project as a new file, make a copy of it, or upload it to the cloud—even when the project identifier has changed.

Learn more about how to control access to in-app comments here: Linked Review 360 Items