Release Notes Version 4.28 June 2015

Summary

The following are some major enhancements in Gainsight Version 4.28 released in June, 2015.

• This release includes the ability to use calculated fields as a filter in reports, more control over searching in CoPilot and reports, and the ability to tag users or groups using Chatter.

• With this release, schedules associated with existing rules that are in the OFF state will be deleted.

Enhancements

This section describes the enhancements made in Gainsight version 4.28.

Reporting

The following enhancements are made in Reporting:

1. Enhancement Location: Administration > Reports 2.0


Description: For opportunities that have multiple accounts, The Account Lookup field now populates with all related accounts, and lets you select a specific account.

A common use case is a parent and a child account, which represent the overall company and region, have a relationship with the same opportunity.

2. Enhancement Location: Administration > Reports 2.0


Description: In MDA, while building a report only on the MDA data, you can now add a calculated measure as a filter and perform aggregations on it.

Note: A calculated measure is created using the tenant management application.

For example, in MDA, if you have defined a calculated measure named Total Messages to contain the total number of messages received from mobile and desktop devices, Total Messages = Mobile Messages (MDA field for mobile messages) + Desktop Messages (MDA field for desktop messages), then while applying filter conditions you can use the Total Messages calculated measure. For example, ”Total Messages > 100”.

3. Enhancement Location: Gainsight Home, CS360, Opportunity Widget, and Account Widgets.


Description:  Search boxes with operators now appear under each column for records in the Grid view. This feature can be used on Gainsight Home, CS360, Opportunity Widget, and Account Widget pages.

Rules Engine

The following enhancements are made in Rules Engine.

1. Enhancement Location: Administration > Rules > [Click on any of the existing rules]


Description: If the rule status is switched from ON to OFF state, any schedule associated with the rule gets deleted.

Note: The proposed MDA upgrade will wipe off schedules of all rules that are in OFF state, even when the client did not choose to upgrade to latest managed package.  This is done as a part of MDA upgrade, which happens well before the Managed package upgrade.

2. Enhancement Location: Administration > Rules > Schedule


Description: In the rules engine you can schedule a rule to run for historical periods, which is typically a 1-time activity. If user edits this rule, the normal use case is NOT to run again for that historical period, which is what we have been doing. In this release, the UI better reflect what is happening in the backend - the check box is automatically unchecked and the following info message is provided.

3. Enhancement Location: Administration > Rules > Setup Rule


Description: While setting up a rule for Matrix Data, you can now use a calculated measure field.

For example, if you have created a calculated field named Utilization from the tenant management application with a custom formula, you can use this field while setting up a rule.

Customers

The following enhancement is made under the Customers tab.

Enhancement Location: The Customers & Engagement tab.

Description: On the Customers & Engagement tab, the content that appears in the Grid view can now be copied.

Issues Addressed

This section describes the issues addressed in version 4.28.

Customers

The following areas are addressed in Customers:

1. Issue Location: Customers > [Click on any of the existing customers] >Summary


Description: When a Website URL containing https was entered in the URL field, on the Summary widget, a redundant https got appended with the URL. For example, if https://www.abc.com was entered in the URL field, on the Summary widget, the URL appeared as https://https://www.abc.com.

Fix offered: This issue is now  resolved. URL is now being validated for redundant https. 

2. Issue Location : Customers > [Click on any of the existing customers] > Opportunity Record Type widget


Issue Description: When an opportunity was being added using the Opportunity Record Type widget, the user was unable to select record types before creating an opportunity.

Fix Offered: This issue is now resolved. Before, creating an opportunity the user can now select the appropriate Opportunity Record Type.

3. Issue Location : Customers > [Click on any of the existing customers] > [Widget using which you can create a task]


Description: When a task was created using the Customer 360 widget, by default, the task being created was related to Opportunity instead of Account.

Fix Offered: This issue is now resolved. Now, when you create a task using the Customer 360 widget the task, by default, is related to Account.

4. Issue Location: Customers > [Click on any of the existing customers] > Usage


Description: When the usage data was configured with the user level data and the user’s org time zone was same as that of the system time zone, data did not appear in the Usage widget.

Fix Offered: This issue is now resolved. Now, even if both the time zones are same, you can see the appropriate data.

5. Issue Location: Customers > [Click on any of the existing customers] > Usage


Description: Under Administration > Usage Configuration, for Instance Level data granularity, the data appeared in the Usage widget only when Enable Account Level Aggregation was selected and Run Aggregation was executed.

Fix Offered: This issue is now resolved. The data is now populated in the Usage widget even if Enable Account Level Aggregation is cleared and Run Aggregation is not executed

Reporting

The following issues are addressed in Reporting.

1. Issue Location: Administration > Reports 2.0


Issue Description: When a large amount of data was fetched, the request timed out. However, we displayed the error as No Data Found.

Fix Offered: This is now fixed.  in case of large amount of data, we now provide the following message: Unable to render report as the query timed out

2. Issue Location: The Customer 360 page.


Issue Description: When a report was viewed in Customer 360, the report fetched incorrect data.

Fix Offered: This issue is now resolved.The report if viewed in Customer 360 now fetches appropriate data.

3. Issue Location: Administration > Reports 2.0


Description: After generating a report that contains a date column, if the searchable date field (as highlighted in the image below) was used, the application was unable to find the entered date.

Fix Offered: The issue is now fixed. The entered date can now be searched.

4. Issue Location: Administration > Reports


Description: When generating a report on scorecards, the color configuration for the generated report did not work as expected.

Fix Offered: This issue is now resolved. The color configuration for scorecards now works as expected.

Rules Engine

The following issues are addressed in Rules Engine.

1. Issue Location: Administration > Rules > Setup Rule


Issue Description: While setting up a rule, if a date filter was used, then by default, the Check for Null Values check box appeared. This was an incorrect behavior.

Fix Offered: This check box is now removed. However, this checkbox will appear if a custom date field is used in Filters.

2. Issue Location: Administration > Rules > Schedule


Issue Description: The end date of a schedule could not be removed.

Fix Offered: This issue is now resolved. You can now remove the end date of a schedule so that the scheduled rule can run periodically without an end date.

Known Issues

This issue describes known issues.

1. Known Issue Location: Administration > Rules > [Click on any of the existing rules]


Known Issue Description: When a rule that is scheduled to run on daily basis is switched to OFF state, on the rule details page under the Rule Info section the scheduled Next Run is displayed, which is an incorrect behavior.

2. A calculated measure field, which is added using tenant management on an MDA collection, will be visible while performing the Load to MDA action. Operations, such as insert or update, cannot be performed on this field. Therefore, if an action (rule) is configured to to load data into a calculated measure field, the rule will fail.