Currenlty when you create a CTA with the 'once in a lifetime' rule logic and you also include the name in the identifiers it'll fire off the CTA using the name, type, reason, and rule action ID as it's identifer. However in the event that the CTA name breaches 80 chars or more it'll trip up and won't use the name as an identifier which may trigger a CTA that should'nt have been triggered. This is particularly a problem for rules that use tokens in the CTA name sense you're never sure what the char count might be.
It would be nice in the future to either raise the char limit on the CTA name or have the logic check of the CTA happen before the rule cuts off the CTA name at 80 chars so that it takes the CTA name logic into account.
Page 1 / 1
I 100% agree with this.
It seems that root cause of this issue (and other similar ones) could be that our Rules Engine compares the CTA Name exactly as configured in the Action (including trailing spaces and any extra characters > 80) against existing CTA Names.
However, when a new CTA is actually created by the Rule Action it truncates the CTA Name to comply with the 80 characters limit and ALSO strips off any trailing spaces (e.g. "My CTA Name with trailing spaces " becomes "My CTA Name with trailing spaces").
To solve this as Andrew stated above, the CTA Name checking logic should be changed so that the Rules Engine truncates the resulting CTA Name and strips off any trailing spaces BEFORE it does the check for existing CTAs by Name when the “Include in Identifiers” for the CTA Name is selected.
Thanks again Andrew!
It seems that root cause of this issue (and other similar ones) could be that our Rules Engine compares the CTA Name exactly as configured in the Action (including trailing spaces and any extra characters > 80) against existing CTA Names.
However, when a new CTA is actually created by the Rule Action it truncates the CTA Name to comply with the 80 characters limit and ALSO strips off any trailing spaces (e.g. "My CTA Name with trailing spaces " becomes "My CTA Name with trailing spaces").
To solve this as Andrew stated above, the CTA Name checking logic should be changed so that the Rules Engine truncates the resulting CTA Name and strips off any trailing spaces BEFORE it does the check for existing CTAs by Name when the “Include in Identifiers” for the CTA Name is selected.
Thanks again Andrew!
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.