These was raised by several users at HPE:
The request is to have Gainsight enable dependencies between different fields, specifically on the CTA object.
Some key examples include having the ability to limit the "Reason" codes that show based on the CTA type (e.g. if CTA type A is chosen, show only reason codes B and C), but this logic can be extended throughout Gainsight fields.
Is this a planned enhancement?
Gainsight fields should follow field dependencies - choice in one field could limit/set value for another field
None
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 username or e-mail address. We'll send you an e-mail with instructions to reset your password.
However, the field dependency is not working there, on the success plan template. This is at the R360.
In addition to that, we utilize the picklist object a lot with features like this. Making it nearly impossible to set a dependency on them. Is there any plan in the future to have the ability to determine a picklist off a picklist lookup?
However, the field dependency is not working there, on the success plan template. This is at the R360.
In addition to that, we utilize the picklist object a lot with features like this. Making it nearly impossible to set a dependency on them. Is there any plan in the future to have the ability to determine a picklist off a picklist lookup?