This technote indicates how to set a color palette for our graphics.
I have set the color scheme to use our brand's colors - this way any graphic presented inside emails sent to clients will be harmonized with the banners and other material we produced.
We use relationships to segregate the CS data for each brand in our company. Some companies may segregate products with relationships. Different brands or products do not necessarily share the same color schemes.
Is the color scheme system wide?
If so, how about an enhancement to allow the setting of color schemes to be by relationship?
Can we set a color palette to be relationship specific?
Hi Diane,
As you noted, the color scheme is system wide as it's related to that specific object - so anywhere that object is used in reporting, the visualizations will reflect the color scheme chosen.
I'm assuming from your example that you might be sending out reports to customers showing details about their usage of your products? One possible way to accomplish the custom color branding that you mentioned would be to create a separate table to store the data that you intend to send to your customers. This would allow you to set product relationship specific colors for each product relationship object.
You could still keep all of the primary data in the current tables, and accomplish this by using a rule to copy the relevant data to the new product relationship specific objects that would be used only for reporting purposes.
As you noted, the color scheme is system wide as it's related to that specific object - so anywhere that object is used in reporting, the visualizations will reflect the color scheme chosen.
I'm assuming from your example that you might be sending out reports to customers showing details about their usage of your products? One possible way to accomplish the custom color branding that you mentioned would be to create a separate table to store the data that you intend to send to your customers. This would allow you to set product relationship specific colors for each product relationship object.
You could still keep all of the primary data in the current tables, and accomplish this by using a rule to copy the relevant data to the new product relationship specific objects that would be used only for reporting purposes.
Reply
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.