In dynamic programs it is very difficult to identify missing tokens in Cloned programs. We support over 20 languages and have a version of each for each template. Some of our Programs have 5 emails and each email can have 5-8 tokens, meaning this needs to be re-mapped hundreds of times. Currently, the missing token looks exactly like the mapped tokens in cloned programs, including the required from fields. See the screen recording on ticket 302972. The ideal solution is that the mappings hold and do not need to be changed at all. That allows for accurate testing in a cloned program. If that cannot be accomodated, or the source changes and the field is truly no longer available, the warning sign should appear and the missing tokens should be red or another color so they can easily be identified and corrected.
Page 1 / 1
This is critical.
We also have programs with multiple variants with numerous tokens.
Advanced JO doesn’t even allow you to save, or to move from one variant to the next if there is even one unmapped token (and the unmapped tokens appear in red).
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.