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.
Page 1 / 1
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.
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!
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.