Implemented

Localizations in Cloned Engagements

  • 26 October 2020
  • 2 replies
  • 61 views

Userlevel 4
Badge

Currently, locatiozations won’t carry over in the cloned engagements. It will save a lot of time if the clone feature can also include the localizations along with the other configurtions like custom CSS.


2 replies

This would help with efficiently managing engagements. We essentially have one engagement that needs to be leveraged on different schedules and environments. Ideally, the user creating the clone could decide whether or not they want localizations included. 

Userlevel 3

Hello Everyone!

Happy to announce that your request has been considered and included as part of the January release. You can now include the localization XLIFF configuration from the source engagement when you clone an engagement.

Thanks for posting!

Reply