Options
Tags:
Related
Recommended

Trados Enterprise - 23.06.1 Release

Ian Parnell
Trados Enterprise - 23.06.1 Release

We have just released the latest update to Trados Enterprise translation management capabilities, and we would like to share the new functionality that has been delivered. New features and updates are automatically added to your account, so just login to Trados Enterprise, and they will be available immediately.

Vendor reassignment flexibility

We have introduced greater flexibility when assigning tasks between vendors and other types of users, or from one vendor to another vendor. Prior to this update, a task could not be reassigned once it had been assigned to a vendor order template. This restriction has now been lifted so it is now possible to assign from a vendor order template to another user or group, or from the currently assigned vendor order template to another vendor order template. 

Note: this reassignment option is available for existing tasks and not when planning future phases from the project workflow. 

When reassigning to a different vendor order template, it is also now possible to specify a prefix for the newly generated vendor order template quote, and also specify the assignee for the Vendor Quote Approval task.

Same source and target language projects

With this latest update, it is now possible to create projects using the same source and target language. This raises several possibilities, including the ability to offer source language editing services, optimize content upstream for consistency and adherence to any language-specific rules or guidelines, but also to optimize machine translation output when the content is subsequently sent for translation into other languages.

Note: Trados Studio does not currently offer support for same source and target language projects. The functionality is therefore initially available for projects managed directly through Trados Enterprise and where linguistic tasks are handled using the Online Editor. Users will be presented with appropriate messaging in the application where project(s) containing the same source and target language must follow this online-only way of working.

TQA feedback available to linguists

When a reviewer performs a Translation Quality Assessment on a document and sends it back to translator to improve the quality of the work, the translator can now see and accept the individual TQA issues that were raised by the reviewer. Previously, the TQA issues were not visible to the translator and another method of communication was required. 

Custom Reporting enhancements 

  • The Short Project ID field, recently introduced in Trados Enterprise and Customer Portal, is now available when using the Custom Reporting module in Trados Enterprise. 
  • We have added a new formula, “EXTRACT_VALUE”, that can be used to extract values from Custom Fields via the Custom Reporting module. More information on the new formula is available in the online documentation here. 

API updates 

  • We extended the information provided for both source and target files in a task with the name, the version and originatingTaskId details 
  • We made available a new rate-limits endpoint and a new header which includes the relevant policy name, namely, the X-RateLimit-Policy header. Read the API-rate-limits page for more details. 
  • We improved descriptions for the default and required fields here. 
  • We updated the JAVA samples to reflect changes in the SDK. 
  • Various bug fixes  

For more details, please visit the What's New page 

Additional changes 

  • Visual improvements in the Project Templates, Workflows, Pricing Models and Translation Engine pages so resources containing many language pairs are now grouped by source language when displayed as a tooltip.
  • Various bug fixes and UX enhancements. 

We hope this post was informative and we look forward to continuing to provide you with updates to the product.

Trados Product Management 

  • in reply to Iris Düwel

    Is there any news on this issue? It would be great to get some feedback if I understood everything right. We really have to solve this issue for us quite soon.

    Thanks so much for your support!

  • We have received a number of questions relating to the vendor reassignment functionality included in the latest update for Trados Enterprise which went into Production earlier this month. I therefore wanted to provide more details on what is possible, following this release, and how this functionality will be extended further in future releases.

    It is now possible to assign to a different vendor during the Project Planning task, so long as you are using one of the standard workflow templates - not a custom one - and this is the first instance of the Project Planning task in the workflow. In a future release, we will extend this functionality to support assignment at the first Project Planning task where a custom workflow template is being used.

    After Project Planning, we have introduced reassignment functionality to cover the scenario where the vendor initially assigned to a task is no longer able to complete that task and the work should be reassigned to a different vendor. In practical terms, you can therefore reassign to a different vendor where the corresponding task exists. Let me explain this further by means of an example.

    The translation task for French in my project is assigned to Vendor A following the Project Planning task. The file passes through Vendor Quote Review and Vendor Quote Approval before arriving at the Translation task. At this point, Vendor A informs me they are no longer able to work on the task, so from the Project > Stages view, I can reassign the Translation task to Vendor B. I am only able to reassign after the Vendor Quote Review and Vendor Quote Approval tasks have been completed and the Translation task has been created.

  • Thanks for the new release. Good to see all those improvements.

    Regarding vendor reassignment flexibility and your note:

    Note: this reassignment option is available for existing tasks and not when planning future phases from the project workflow. 

    This is not quite what we were expecting and promised, to be honest. What we need is the possibility to reassign to a different vendor during project planning BEFORE we send the project to a vendor. We have different vendors for one client and need the flexibility during project planning to reassing to a different vendor for various reasons. The client cannot decide on the vendor, as we project managers know when to assign to somebody else.

    When will it be possible to reassign to a different vendor during project planning?

  • in reply to Luis Lopes

      That's great but I'm not sure I understand your note. Could you please clarify a bit "this reassignment option is available for existing tasks and not when planning future phases from the project workflow"?

  •  , See above. Looking forward to your feedback if we can improve on the vendor reassignment functionality.