Authors
Video Tutorials
Articulate Localization: Streamline Language Validation With Review 360
Articulate Localization leverages the collaborative workflows in Review 360 to speed up the process of human validation for AI translations. Once you publish your multi-language course to Review 360, you can assign validators to review the AI translation and keep track of their progress. Watch this video to learn about the validation experience for authors and validators using a multi-language Rise 360 course. Then read on for more detailed steps.
Publish to Review 360
To get started, publish your multi-language project to Review 360. Refer to these user guides for specific details on the publishing process:
As shown below, you can choose to include all project languages or just a subset when you publish after translating with Articulate Localization.
Storyline 360 | Rise 360 |
When publishing is complete, launch your Review 360 dashboard. The source and target languages are presented as a single "stack" tile. Clicking the tile opens an overview page that lists all the current languages in a sidebar and allows you to preview each language.
Note: Multi-language courses can only have one corresponding stack in Review 360. Republishing to Review 360 creates new versions of the languages in the stack. Duplicating content in Rise 360 creates a new course, resulting in a new stack in Review 360 when published. However, Storyline 360 preserves the link between the project file and the Review stack when you create copies of the file—for example, using Save As or sharing the file with other authors. If you need a new stack in Review 360, use Save Translation As to create a copy of the source language, translate or add the languages you need, and then publish. |
Request Validation
To request a language validation, click the Request Review button on the top right for each target language you want validated. Then, follow the standard Request Review workflow. Note that:
- Language validators do not need to be Articulate 360 seat holders. As with any other Review 360 item, reviewers only need an email address.
- For a validator, each language in the stack functions like its own Review item. They will not see the stack or be able to access other target languages unless they are also an Articulate 360 seat holder with appropriate permissions.
- The request review status is displayed on the sidebar and on the top right button for the corresponding target language. The status can be:
- Request Review: You haven’t assigned any reviewers.
- In Review: You have assigned reviewers who haven’t completed the review.
- Review Complete: All assigned reviewers have completed their review.
- If you share the item in team folders, editors will see the overview page and can assign reviewers for target languages.
Here's a comparison of how an author and a validator see a Review 360 item for validation.
Author's view | Validator's view |
Validators can suggest text changes and preview those changes in real time. To learn more about the validation experience from the perspective of a validator, check out this guide for language validators. You can also share it with your validators for their reference or share the course version to provide it in their preferred language.
Once a validator has finished their review, you can import their suggestions. Instructions for importing validator suggestions can be found in this user guide: Articulate Localization: Import Suggestions from Language Validators.
Request Validation for Updates
If you need to make changes after validators have completed their review, follow these steps to ensure your updates are properly translated and validated:
- Follow the steps to translate the updates in Rise 360 or Storyline 360.
- Publish a new version to Review 360.
- Let your validators know. You can restart the request review process to notify the same validators about the update and reset their review status or start a new request for different validators.
Here’s additional information about how this works:
- Validation status rolls forward with each new version published.
- Review 360 identifies updates for validation by comparing the current version with the previous version of the Review 360 item.
- If you need to edit the course after publishing the updates to Review 360, restore the Review 360 item to the previous version first before republishing to Review 360. This ensures all the updates are correctly identified for validation. Keep in mind that restoring previous versions will permanently delete newer versions, their comments, validation, and any unimported suggestions.
- Avoid republishing another version before pending updates are validated. The new version becomes the reference for comparison, so Review 360 may not detect earlier updates.
- When validators view the content, they can click the Validate Updates button to start the course update validation workflow and go through each updated segment. Learn more about validating updates.