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.
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.
Reply
Login to the community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.