Object is reused in two books, import of translation jobs in 'wrong' order


This process describes the behaviour of the flag for re-translation when you have two books that use a topic, and the object is modified and included in the translation job for the second book. But job 2 is imported before job 1.

  1. 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 for book 1 (job1)).
  2. The flag for re-translation appears on the locale variants of that primary object.
  3. Book 2 reuses that object. A user creates a translation job for book 2 that contains that primary object for that language (job 2).
  4. As soon as the translation job 2 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.
  5. When you import translation job 2, the state of the object variant is changed to the import state (e.g. Translation Review), because this job contains the latest version of the object.
  6. When you import translation job 1, the import of the local variant is skipped, because it is based on a previous version of that object.