Translation Organizer should facilitate associating a single translation job with multiple primary TM configurations, to ensure all files in the job are translated against the correct primary TM automatically.
Currently, when a translation job is created in Translation Organizer, a user must select a translation template that routes the files or translation against one primary TM, and other secondary TMs. This can impact translation matching, accuracy, and costs. In order to translate the files against different primary TMs, the user must create multiple, separate TM jobs for individual topics from the same publication. This is inefficient and error-prone.