This process describes the behaviour of the flag for re-translation, when you do two imports for the same job. For example, when you have your translation reviewed, you want to import the updated xml for the same translation job again. But in-between the two imports, you start a translation job that includes the object that is flagged for re-translation. In that case, it is important that the release state on the second import does not change:
- A user edits the primary object in the source language. A locale variant of that object is out for translation (included in a translation job).
- The flag for re-translation appears on the locale variants of that primary object.
- When you import the translation job to publish output for review, the flag is not removed (because the translation was based on a previous version of the primary object).
- A user creates a translation job for a book that contains that primary object for that language.
- The flagged locale variant will be included in the translation job. The release state of the variant changes to the export release state, e.g. 'Sent for Translation'.
- As soon as the translation job is 'Created', the flag for re-translation is removed from the locale variant. The variant shows the full color flag again. From the release state, you can see that the object is sent for translation, and has content that is not yet up-to-date.
- When you do an import of the final translation job xml of the 'old' translation job, the flag is not removed (because the translation was based on a previous version of the primary object). However, the state of the object variant is not changed to the import state, because there is still an open translation job that includes this object.
- The state of the locale variant changes to the import state on import of the second translation job.