Forum Discussion
Language Verification
Hi KarlCartwright-,
You’re right. Publishing an updated version of your Storyline course to Review 360 updates both the course and its translations. Here’s what happens and how it affects language validation:
When you publish updates, Review 360 creates a new version for each language in your project. Language validations don’t carry over automatically, so validators will need to re-review the content to ensure it aligns with the latest changes.
To push updates, use the standard Publish to Review 360 option in Storyline. This will automatically update the language versions in your validation workflow.
To help streamline the review process, you can highlight or mark updated content in your course so reviewers can easily focus on what changed. This is a standard best practice in localization workflows.
For more details, you can refer to this article: Articulate Localization: Get Started with Language Validation in Review 360
Please don’t hesitate to reach out if you have additional questions.
Thank you. I will check this.
I am able to publish a new version of the course through Review 360. What I am not seeing is the ability to publish a new version of Language Verification. If the Language Verification publish and a Review 360 publish do the same thing, then its not entirely understood through the Storyline Interface.
After doing a new translation, there is no option to publish Language Validation again. So I thought I needed to remove the old Language Verification publish, to upload a new one.
But if I understand you correctly, publishing to Review 360 ALSO updates the laguage Validation.
So, maybe pulish through the Laguage Validation option is not entirely necessary, since publishing through Review 360 does the same thing? But whichever way you initially publish for Lanuage Validation, you need to publish any updates through the Publish to Review 360 option.
Do I understand that correctly?
Hi KarlCartwright-,
You’re right. Publishing an updated version of your Storyline course to Review 360 updates both the course and its translations. Here’s what happens and how it affects language validation:
When you publish updates, Review 360 creates a new version for each language in your project. Language validations don’t carry over automatically, so validators will need to re-review the content to ensure it aligns with the latest changes.
To push updates, use the standard Publish to Review 360 option in Storyline. This will automatically update the language versions in your validation workflow.
To help streamline the review process, you can highlight or mark updated content in your course so reviewers can easily focus on what changed. This is a standard best practice in localization workflows.
For more details, you can refer to this article: Articulate Localization: Get Started with Language Validation in Review 360
Please don’t hesitate to reach out if you have additional questions.