Salesforce

WorldServer - How to bypass the QA Checker results if the issue found should not be corrected from a linguistic point of view

« Go Back

Information

 
TitleWorldServer - How to bypass the QA Checker results if the issue found should not be corrected from a linguistic point of view
URL Name000006458
SummaryIt is currently not possible to mark the error as false positive. It is - however - possible to configure the Workflow to bypass the QA Checker step when required. This article explains how to do this.
Scope/EnvironmentWorldServer
Question
Starting from WorldServer 11.3., a new functionality and a new Automatic Action called QA checker has been introduced. You can learn more about this Automatic Action in the RWS Documentation Center and in the Additional quality assurance options section of the New in WorldServer 11.3. page. Here you will also find a video demonstrating how to implement this step in your Workflow.

The default configuration of a Workflow that includes the QA Checker Automatic Action includes 2 options/transitions.

1. Accepted or Passed - all QA checks ended with the result PASS and the Auto Action is moving the project to the next step in the Workflow.

2. Rejected or Failed - one or multiple QA checks ended with FAIL and the Auto Action is returning the project into the previous step in the workflow e.g. Translate.

The QA Checker step is not taking the possibility into consideration that it may be necessary to inflect the translation of a term for some languages, place tags in the target segment differently than in the source segment or replace a number by a word. Example: 

"1 year subscription" is translated as "ročné predplatné" in Slovak language. The QA Checker will find a missing number and report this as an error. It should be possible to mark the error as false positive as otherwise the translation will never reach the next step. Alternatively, allow the translators to have an option to skip the QA Checker step when the translation is rejected based on false positive QA result.

Answer
It is currently not possible to mark the error as false positive. It is - however - possible to configure the Workflow to bypass the QA Checker step when required. This is an example of a very simple Workflow showing how this could be done:

User-added image
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by