Release Notes Version 5.16 July 2018

Survey Links

• Survey 1.0 issue (broken links) can be resolved with the latest Salesforce update: Enable the Allow topics in Salesforce Sites and Portals option from Salesforce Setup > Chatter > Chatter Settings for the guest and authenticated external users to have access to the topics in Salesforce Sites and Portals.

Note: If your org was upgraded to the SFDC Summer 18 release, you may face this issue (such as broken Survey Links, etc.). The Allow topics in Salesforce Sites and Portals option will be available for you to select on/after July 19th when Salesforce will implement the permission on the Topics object in their production org.

Impacted areas:

• Survey 1.0 (Breaking in the area where response is captured.)
• CoPilot > Outreaches > Survey

CoPilot/Advanced Outreach

• CoPilot and Advanced Outreach name change: CoPilot is renamed Journey Orchestrator and Advanced Outreach is renamed Programs. The name changes for these features will be visible throughout Gainsight and will not affect the functionality of these features. The names of the data objects associated with these features have not changed. 

Rules Engine

•  In Rules > Setup Action > Action type dropdown list, Load to MDA Subject Area is now renamed Load to Gainsight Object.

• *Custom Rule deprecation plan*: After Gainsight's October 2018 release, all new rules must be created as Bionic Rules. Your existing custom rules will continue to run and still be editable. Although Gainsight is developing a utility to migrate custom rules to Bionic Rules, we recommend that Admins begin reviewing their custom rules to look for opportunities to combine multiple rules into single Bionic Rules. You'll have plenty of time for this process which is outlined in this FAQ. 
  
  Please see this series of articles for assistance in creating Bionic Rules. We also offer a free e-learning course on Bionic Rules. 
  
  If you aren't familiar with Bionic Rules, watch this 2-min. video to learn how they're more powerful than custom rules, but not that different in terms of how to configure them!

Gainsight Data Management

1. Option to delete records from the Data Operation page: You can now delete records from the Company and Relationship objects in the Data Operation page.
   
   CAUTION: Once you delete a record from the Company or Relationship objects, you cannot recover the record later.
   
   To delete records from the Company and Relationship objects:
   1. Navigate to Administration > Data Operation.
   2. Select either the Company or Relationship standard object from which you want to delete records. Records from the selected object are displayed.
   3. Select the checkbox next to the record that you want to delete.
   4. Click the Delete record icon to delete records that you have selected. Delete Record dialog appears.
   5. Before deleting records, you can check other object dependencies on the current object by clicking link to Object Dependencies as shown below. Object graph of the current object is displayed.

Note: When you first click this link, it takes some time to load the object graph and the system notifies you of the small delay. When you click the link subsequently, the objects graph loads and displays instantly.

6. Click CONFIRM to proceed with deleting the records that you selected.

The following image shows how to delete records from the Data Operation page:

After records are deleted from either Company or Relationship object, fields in other objects that have MDA Joins with either of these objects honor the option selected in the MDA Joins On Delete option in that field. For more information, refer Gainsight Data Management.

Note: You cannot delete records from the User or Person object.

2. Resync option in the Object Graph: When multiple objects are joined through custom fields, rarely these MDA Joins do not appear in the object graph of some objects. A new resync button is introduced in the object graph for every object. If you observe that there are any missing MDA joins in any object graph, click the resync button in the object graph. It resyncs all of the resources to the MDA database and displays any missing MDA joins.
   
   This issue is very rare and resync should not be applied on a regular basis. The resyncing operation takes some time depending on the number of joins between multiple objects in MDA.
   
   To see this option in the UI, navigate to Administration > Data Management > [Select an object] > [Click Object Graph].

 

3. Set the default for ‘On Delete’ option in MDA Joins: While applying MDA joins on a custom field in any standard or custom object, the ‘On Delete’ option is selected as None by default. You can now change the On Delete option from None to Set Null or Delete as required, except for MDA joins from or to User/Person object fields.

Note: In Gainsight orgs with version V5.15.2 or earlier, On Delete option in the MDA Joins was selected to Set Null by default. This is changed now.

4. Controller and Dependent fields in an Object: A new section Dependent Categories is added to the Dropdown Lists page. You can add fields on the Dependent and Controller Categories and create a Relationship between them as Controller and Dependent. When these fields are used in any consumption area, system allows users to select the item(s) in a Dependent field based on the selection of an item in the Controller field. To see Dependent categories section, navigate to Administration > Data Management > Dropdown Lists.
   
   Controller: It is a category which has a list of dropdown items. Each item in the controller can control a set of items in another category (Dependent). 
   
   Dependent: It is a category which has a list of dropdown items. Some or all items in the dependent category can be in correspondence with an item from its Controller category. 
   
   Note: Category is a Dropdown List that contains a list of items.
   
   Example: When you want to store Country and State of a CSM location in an object, you may create a field Country and map to a Dependent category named State. When a user in a consumption area selects an item in the Country field, another dropdown list appears to select a State also.
   
   To create Controller and Dependent fields in an object:

1. Navigate to Administration > Data Management > Dropdown Lists.
2. Add a Controller Category (Ex: Country) of Single select type and add items (Country names). For the detailed information about how to create a category and items in a category, refer Dropdown List and Multi Select Dropdown List.
3. Add a Dependent Category (Ex: State) of Single or Multi select type and add items (State names).
4. Click +DEPENDENCY in the Dependent Categories section in the Dropdown Lists page.
5. Select Controller (Country here) and Dependent (State here) categories from the respective dropdown lists.

Note: Controller dropdown list shows only categories of Single select whereas Dependent dropdown list shows both the Single select and Multi select categories.

6. Select an item from the Controller category (one Country name) on the left pane and its corresponding items from the Dependent category (State names here) on the right pane.

7. Click SAVE. Items in a dependent category are now mapped with the respective items in a controller category.

8. Navigate to Administration > Data Management > All Objects. Select an object in which you want to create Controller and Dependent fields.

9. Click ADD FIELD and create a field (Country here) of data type Dropdown List and map to the category Country that has been added in Step b. For more information on how to create a field in an object, refer Gainsight Data Management.

10. Add another field of data type Dropdown List and map to the category State that has been added in step 3 and select Controller as Country as shown below. Dependency between Dependent and Controller fields is now created.

In a consumption area where data from the User object is used, if a user selects a Country, the corresponding item State can also be selected. For more information on how these dependent fields are used in Timeline feature, refer the section Timeline.

Note: You can create dependent fields of single select or multi select dropdown list data type whereas you can create controller fields of single select dropdown list only. This allows users to select multiple items in a dependent field.

Scorecard

• When a record from the company or relationship object is deleted, the corresponding scorecard data (from the corresponding fact and history objects) is deleted. For more info, refer to the first enhancement under the Gainsight Data Management section. 
  
  Note: There is no way to recover the deleted data, so be sure before deleting Company and Relationship records.

Reporting

•  URL Data type in Reporting: When you build reports using the fields with URL data types, the field displays a clickable hyperlink.
  
  Notes:
  • URL data type support is applicable only for MDA objects but not for SFDC objects.
  • URL field is not supported in ‘By’ fields.

Surveys 2.0

• Custom pages for Surveys 2.0 Thank You messages: Admins can now select a custom page to display as the Thank You message in a Surveys 2.0 survey. Survey participants will navigate to this page automatically after completing the survey.
  
  To select this option, open your Surveys 2.0 survey and navigate to Properties > Additional Configuration > Visual Experience > Thank You message and select Custom Page. Once the Custom Page option is chosen, you can select a page using the field below. For more information on the options available on the Surveys 2.0 Properties tab, refer to Survey 2.0 Properties.

 

Only pages configured under Administration > Pages will be available to be selected as a Thank You message. To learn more about creating pages, refer to Setup a Gainsight Domain.

After a custom page is selected as the Thank You message for a survey, only the site associated with that page will be an option to select on the survey distribution tab. For more information on selecting sites for survey distribution, refer to Distribute Surveys 2.0.

Journey Orchestrator (formerly, CoPilot)

1. CoPilot and Advanced Outreach name change: CoPilot is renamed as Journey Orchestrator and Advanced Outreach is renamed as Programs. The name changes for these features will be visible throughout Gainsight and will not affect the functionality of these features. The names of the data objects associated with these features have not changed.
   
   Note: We are currently working on updating the images within our documentation to reflect this change and expect to complete this process by end of July. Until then, You may encounter screenshots that display the terms CoPilot and Advanced Outreach. Thank you for your patience as we make this change.

2.  View Failed Participants List: You can now view a list of failed participants  which are not added to the Programs for some reason/s. The list is generated after participants are synced (manually or via schedule) after unique and advanced criteria are applied.
   
   The list includes a column displaying the reasons for failure. The following table lists the conditions for which participants might fail to sync and the message associated with that condition:

Condition	Failure Message
Unique Criteria	Participant filtered due to unique criteria
Don’t Send Emails in X days	Participant filtered due to advanced criteria
Hard Bounce	Participant email address part of hard bounce list
Soft Bounce	Participant email address part of soft bounce list
Unsubscribed Email	Participant has unsubscribed from Survey/CoPilot Emails
Invalid Email	Invalid Email Address
Exclusion List CSV	Participant part of CSV Exclusion List uploaded into the advanced outreach
Operational Email - Rule 1	Operational Email - More than 5000 active participants in the advanced outreach
Operational Email - Rule 2	Operational Email - More than 5000 participants synced per day
No Sfdc Account Id or Company Id or Sfdc RelationShip Id or Gs Relationship Id	Participant Account/Relationship Id not synced correctly

You can view the Failed Participants list by navigating to the model configuration of a Program > Participant Configuration and clicking the Participants icon.

You can then view either the Participants or Failed Participants list by clicking the associated tab.

For more information on adding and viewing participants in a Program, refer Adding Participants to a Program.

3. Add Custom Email Fields to Programs: Admins can now include custom email fields in a Program’s email. These fields can be used to configure the fields “To”, “Reply-to”, “From Email”, and “Email Copy to”; as well as the tokens within a Program’s email steps. Prior to this release, only the “Recipient Email Address” and “Manager Email Address” email fields could be configured in those areas. The additional email fields are added as custom fields when configuring participant mapping.
   
   You can use this feature to contact people related to the account other than the Participant or CSM as part of your Program. For example, if you needed to reach out to a contact with a third party vendor as part of an email step in the Program, you could map a custom email field to the field containing the vendor’s email address. Then, you could use that custom email field when configuring an email step within the Program.
   
   To add a custom email field, navigate to the Participants Configuration section of your Program and select Mapping Participant Sources > Custom Field Mapping > + ADD CUSTOM FIELD > Email.
   
   
   
   Note: You can add up to three custom email fields to use as part of your Program. 
   
   After the custom field is added, you will be able to map it to the fields pulled in from your participant sources.
   
   
   
   Note: Syntax Validation for the content of the custom email fields will occur during Participant Sync. If the validation fails, the participant will move to the list of Failed Participants. 
   For more information on mapping fields and syncing participants, refer to Adding Participants to a Program. 
   You can select the custom email fields as tokenization options in the Program’s email step.

     For more information on configuring email steps, refer to Configure Model and Emails for Programs.

4. View customer and contact analytics on the new Journey Analytics page: The Journey Analytics page displays data across Programs for each customer and contact. Under Journey Analytics, admins can view information including the number of programs a customer or contact has participated in, as well as out of the box reports for bounce rate, unsubscribe rate, and other data.
   
   Journey Analytics is a new page as of the 5.16 release. To navigate to this feature, select Journey Orchestrator > Journey Analytics.
   
   
   
   The search bar at the top of the page can be configured to search for Customers or Contacts. Click the drop-down arrow by the magnifying glass to display these options. You can then type in the name of the Customer or Contact you would like to search.
   
   

Customer Analytics

1. Back Arrow: This is only visible after a Customer has been selected from the search bar above. Click the arrow to navigate back to the default Journey Analytics page.
2. Programs widget: Displays the total number of Programs contacts associated with the Customer has participated in
3. Contacts widget: Displays the total number of Contacts associated with the Customer that have participated in Programs
4. Total Email Sent widget: The total number of emails sent to Contacts associated with the Customer from all Programs
5. Open CTAs widget: Displays the total number of open CTAs associated with the Customer
6. Open & Click Rate widget: Displays the percentage of delivered emails out of sent emails, the percentage of open emails out of delivered emails, and the percentage of clicked emails out of opened emails for the Customer. These percentages are pulled from all Programs.
7. Bounce & Unsubscribe Rate widget: Displays the percentage and number of Bounced, Unsubscribed, and Rejected emails sent to the Customer. These percentages are pulled from all Programs.
8. Sent, Open, Click Report: Displays the number of emails sent, opened and clicked on by the Customer over time. Users have the ability to filter based on time period, change the report’s visualization type, and other chart options. This report, as well as the Bounced report and Spammed report also on this page, were previously available under CoPilot > Analytics. For more information on configuring these reports, refer to Review Journey Orchestrator Analytics (Reports).

Contact Analytics

1. Customer Info: Name and Email of contact currently displayed. The back arrow will navigate to the default Customer analytics screen.
2. Programs widget: Displays the total number of programs the contact has participated in
3. Total Email Sent widget: The total number of emails sent to the contact from all Programs
4. Open Rate widget: Displays the rate the contact has opened emails sent to them through Programs
5. Program filter: Use this drop-down field to select the Program you would like to see activity for
6. First Entered Program: Displays the date and time the contact entered the selected Program as a participant
7. Email Activity Breakdown:
8. Activity Feed: Displays the contact’s activity feed for the selected program. For more information regarding activity feeds, refer to Programs: Participant Activity Feed.
9. Refresh: Click this to refresh the content of the contact’s activity feed.

Timeline

Fields of Dependent Dropdown List type can now be added in the Activity Type layout Configuration: You can add fields on the Dependent and Controller Categories from Administration > Data Management > Dropdown Lists > +DEPENDENCY. When these fields are used in Timeline, system allows you to select the item(s) in a Dependent field based on the selection of an item in the Controller field. For more information, refer to the 4. Dependent Categories in Dropdown Lists section under Gainsight Data Management.

To use Controller and Dependent dropdown lists in Activity Timeline:

1. Navigate to Administration > Activities and Timeline > GENERAL SETTINGS tab.
2. Click +ACTIVITY TYPE to create a new activity or edit icon of an existing Activity Type (here it is Email) in the Activity Type section. Add or Edit Activity Type dialog appears.
3. Click +FIELD in the Configure Layout section.
4. Provide the following details while creating a field.
   1. Field Type: Dropdown
   2. Name: As per individual choice (Here it is ‘CountryX’).
   3. Category: Controlling dropdown category (here it is ‘Country’).

Notes:

• If you do not see the Controlling Field after selecting the ‘Country’ Category, that means the category you selected is either Controller or has no dependencies. You can create controlling field for Country from Data Management page.
• You can click 'here' to navigate to the Data Management page to add a new category or controlling field from this dialog. Data Management page is opened in a new tab. For more information on how to add a new category, refer Dropdown List and Multi Select Dropdown List.

You can also add fields from the Available fields to the Selected fields. To add dependent fields, add controlling fields first.

5. Click +FIELD again to add the dependent dropdown.
6. Add dependent dropdown. Provide the following details while adding field(s).
   1. Field Type: Dropdown
   2. Name: As per individual choice (Here it is ‘StateX’).
   3. Category: Dependent dropdown (here it is ‘State’)
   4. Controlling Field: Select a controlling field for the Category selected above (CountryX).

7. Navigate to C360 > Timeline  or directly Timeline tab.
8. Click +ACTIVITY.
9. Select the activity type from the dropdown list (here it is Email). The Log an Email dialog box appears.
10. Provide the required information. This dialog box contains the dependent field (StateX) with a controlling field (CountryX).

Note: The items in the dependent category (here, it is the list of states) are in correspondence with the item selected in the controlling category (here, it is the list of countries). Example, if "United States" is selected from the controlling category (CountryX), then only the dependent category (StateX) will be activated and will show the list of states. If you change the country, the corresponding states will also be changed.

Rules Engine

1. Enhanced usage of Formula Fields in Bionic Rules: You can now find different types of formula fields in the left pane, under the Formula Fields section in a Transformation Task. To use a specific Formula type, add it to the Show section. When you add this specific Formula type to the Show section, its respective dialog appears, which assists you in using the formula. 
   
   In Gainsight orgs with versions prior to V5.16, all of these formula fields are referred to as different functions in a Formula field. A new formula field Calculated Fields is added in this version and is explained in the next enhancement.
   
   To use a Formula field:
   1. Create a Transformation task.
   2. Select the Dataset, on which you want to apply the Formulas. You can now view all the formula fields under the Formulas Field section, for different data types.
   3. Drag and drop any Formula type to the Show section. The respective formula field dialog appears. You can create the formula, as required.

To learn more about using different types of Formula Fields in Bionic Rules, refer Formula Fields in Bionic Rules.

The different types of formulas available are:

• Date Formulas
• Statistical Formulas
• String Formulas
• Calculated Fields
• Numeric Expression
• Period over Period comparison  
• Period over Period Comparison in %

2. Calculated Fields in Bionic Rules: You can now use Calculated fields in Bionic Rules > Transformation task. Calculated fields allow you to perform two types of calculations:  

• Aggregation: Aggregation tasks allow you to calculate the maximum, minimum, Count distinct, Sum, average, for a financial metric. For example, you can calculate the average MRR generated by a Company for the past one year.
• Comparison: Comparison tasks allow you to compare the performance of either two different financial metrics over a specific time period, or compare performance of a single metric over two different time spans.

You can use either the actual numerical values or percentages. You can see Calculated Fields under the Formula Fields section in a Transformation task.

To aggregate using Calculated fields:

1. Create a Transformation task.
2. Select the Dataset, on which you want to apply Formulas.
3. Drag and drop Calculated Field to the Show section.
4. Select the Aggregation (over time) option in the Type of Calculation field. You can now perform the required aggregation task.

To learn more about using Aggregation in Calculated fields, refer Using Calculated Fields in Rules.

To compare using Calculated fields:

1. Create a Transformation task.
2. Select the Dataset on which you want to apply the Formulas.
3. Drag and drop Calculated Field to the Show section.
4. Select the Comparison option in the Type of Calculation field. You can now perform the required comparison using two sections as defined below:
   1. Define section A: In this section, select the first financial metric and the related time period for comparison.
   2. Define section B: In this section, select the second financial metric and the related time period for comparison. 
      
      If you want to compare only one financial metric over different time periods, keep the financial metric the same in both of the sections and provide different time periods.

To learn more about using Comparison task in Calculated fields, refer Using Calculated Fields in Rules.

3. Enhancements in the Setup Action page: In the Bionic Rule Setup Action page, if there is only one dataset to setup an action, you can now directly create an action without having to select the Dataset. To see this enhancement:
   1. Navigate to Administration > Rules Engine > Setup Action Page.
   2. Click + ACTION to setup an action. If there is a single dataset, the action is created automatically without having to select the Dataset.

However, if there are multiple Datasets, a drop down menu appears after you click + ACTION and then you can select the required Dataset to setup an action.

Note: In Gainsight orgs with versions prior to V5.16, you had to manually select a Dataset, even if a single dataset existed.

Programs (formerly known as Advanced Outreaches)

• Programs Listview Displayed Incomplete Filter Results: Previously, when certain filters in the Programs list view were applied, only the top 10 results would display, even if more results were available. This has been resolved by enhancing filter functionality.
  
  Note: Your org must have more than 10 Programs of any type to see the enhancement.

Activity and Timeline

• Grammatical error on UI has been corrected: Previously, activity type with the name 'Use Case', that is the "Log an Use Case" option had grammatical error (wrong usage of article) in it. This is now fixed.

Scorecard

• Gainsight Account Widget was showing incorrect Scorecard: Previously, when you logged in, the correct Scorecard was shown in the Gainsight widget, but when you tried to switch between relationships of an account, it was not  changing the corresponding scorecard after you refreshed the page.
• Unresponsive Set Aggregation button in Usage Configuration: Previously, the Set Aggregation button was not functioning in the Administration > Usage Configuration page. This issue is resolved and you can now click the button to access the Column Aggregation Type dialog box to set the aggregation.

• Unable to apply filter for NULL values while excluding NA values: Previously, Habits and standard reports on History/Snapshot were throwing the following error:  "Error occurred while fetching data from external service.” when you applied scorecard name filter (A) and adoption !=null (B) in filters. In changing filter order for adoption != null as filter (A), you got the results. But, when you added scorecard name as filter (B), the first filter was removed and the scorecard name was shown as filter (A). This issues is now and filters are working properly as expected.
• Account Scorecard History showed duplicate dates when the Setup Action > Action Type was selected as Load To Scorecard History: Previously, when you created Bionic Rules with the source object selected as Account Scorecard History in Matrix Data, Load to Scorecard History as Action Type and used upsert operation, the rule was successful but there were duplicate values created in Account Scorecard History. When you built a report on the same object, the duplicate values were observed in the Report Builder as well. This issue is now resolved.

Customer 360

• Grammatical error on UI has been corrected: Previously, when you created an activity type from Customer 360 > Timeline with the name 'Use Case', the option in the +ACTIVITY dropdown showed as "Log an Use Case" which is wrong.(wrong usage of article). This is now fixed. ‘Log a/an’ is now removed from all the options and only the Activity Type names are listed in the dropdown list.

• Widgets checkboxes get unchecked for summary section after reloading page: Previously, when you edit configuration of the Summary section in C360 Layouts > Layout Configuration and save, the widgets were unchecked automatically in reloading the page. This issue is now resolved and the enable/disable checkboxes are working properly as expected. Refer the following image.

Survey

• Error Message Displayed on Survey Page: Previously, the error message, "An exception occurred while trying to retrieve the surveys," would display when users would attempt to access the survey page if there were more than 100 jobs running in the background of their org. This issue has been resolved, and the survey page now displays regardless of the number of jobs running.
• Survey failing to preview when 6 conditions are added in display rule: Previously, surveys would not display a preview when six conditions were added in a display rule for survey questions. This has been resolved, and surveys now preview as expected.
• Picklist field not displaying values: Previously, fields with the datatype picklist were not displaying any values in the set CTA section of Relationship type surveys. This issue has been resolved, and the values are now displaying as expected.
• Opt-out messages displaying for opted-in participants: Previously, the message, "Selected participants are opted out email communication," would display for certain participants who were not opted out of communication. This has been resolved, and this message now only displays when participants have opted out as expected.

Connectors

• S3 Connector Authorization failed: Previously, the error message “Failed to Setup S3 Connector” would display when users would attempt to authorize themselves in the S3 connector. This issue is now resolved and you can now successfully authorize yourself with the S3 connector.

• Data Jobs in the S3 execution Logs were out of order: In the S3 Connector execution logs, S3 execution history does not show the data jobs in the order of the time they were executed because of this all the data jobs are not in a specific order. This issue is resolved now and you can see the data jobs in the order of their time of execution.
• Search field in an Object page does not show all characters: Data Management > Schema Tab > Search field doesn't show all characters while typing the search word in all the columns. This issue is now resolved.

Rules Engine

• Rule Migration Failure: Previously, when the Cross Org Migration tool was used to migrate the Rules, the rule migration failed, if the reference fields were not used in the Rule Show section. This issue is now resolved and you can successfully migrate rules using the Cross Org Migration tools.
• While applying a Pivoting condition in a Bionic Rule Pivot task, if a field of long text is selected in any dropdown, another field label in the screen is either missing or trimmed. This issue is now resolved and Pivoting is working as expected.
• In the Load to Company Person action type, in the field mappings, when you tried to load values into the target fields of data type Date and Dropdown list, the values are not loaded. Loading values into the target field of data type Date from the existing field was also failed. These issues are resolved now and the action type is working as expected.
• If there is a field having self lookup to ID field in an object (Relationship), that field is added to Show section in the Setup Rule page automatically. This field is considered as Relationship resolvable field even after adding Relationship: Id manually into the setup Rule page and results into not showing all action types in the Setup Action page.

Journey Orchestrator (previously known as CoPilot)

• Log to SF Activity from Outreach Failed: Previously, the Log to Salesforce Activity feature for certain outreaches failed due to NullPointerException. This has been resolved, and activity is logged as expected.
• HTML not honoring Table tag correctly in GS Email template: Previously, when a table tag was included in the HTML code, and it was added to a GS Email template, the style did not display correctly. This has been resolved, and style of the tag now displays as expected.
• Power list not pulling the data: Previously, when running a power list with multiple account lookups, the data is not pulling as expected as per the selected account lookup. This has been resolved, and data is now pulling as expected.
• Unable to view long field names in Outreach filters: Previously, it was not always possible to view long field names when they were selected in an Outreach filter. This has been resolved, and there are now options to view long fields names when selected.
• Resizing image issues in CoPilot Email Templates: Previously, images in a CoPilot Email Template would not resize correctly or resize at all. This has been resolved, and it is now possible to resize an image within a CoPilot Email Template without issue.

Shared 360

• MDA Widgets were not working in External Sharing: There was an error found in the shared layout as MDA widget report was not appearing here correctly but it was visible in preview. The same issue was observed in Gainsight 360. This issue is now fixed for both Shared360 and also Gainsight 360.

Survey

• Incorrect button displaying in Surveys 2.0 Properties tab in IE: When navigating from other Surveys 2.0 tabs to the Properties tab, the blue plus icon and the blue checkmark icon displayed in the other tabs will display in the Properties tab. This button will also sometimes appear in the Properties tab when after clicking on a survey from the survey list view. The button does not normally display in this tab. This issue is occurring in Internet Explorer.

Icon used in this Doc	Description
	This symbol indicates that an enhancement originated as a customer suggestion on the Gainsight Community. If you have feedback or questions on the Release Notes, please share them on community.gainsight.com.