Skip to main content

 

Gainsight Inc.

Release Notes Version 5.19 October 2018

For a quick preview of what's new in this release, check out this 8-min. video!

Notifications

  • Gainsight had an interim 5.18 release in which a new Permission set was added; Gainsight Viewer. You can find more info on this new permission set in the Permission set section of this document.

Rules Engine

  • Custom Rule Retirement Plan: With this release, all new rules must be created as Bionic Rules. You cannot create new Custom Rules, but your existing Custom Rules will continue to run and still be editable.

1 Custom Rule Retirement Plan.png

Although Gainsight is developing a utility to migrate Custom Rules to Bionic Rules, Gainsight recommends that Admins begin reviewing their Custom Rules to look for opportunities to combine multiple rules into a single Bionic Rule. For more information, refer Custom Rule Deprecation FAQs.

Please see this series of articles for assistance in creating Bionic Rules. Gainsight also offers a free e-learning course on Bionic Rules. If you are not 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.

Enhancements

Journey Orchestrator

  1. Access to new Email Template Performance Report: Users can view a new, out-of-the-box report to help you understand which Email Templates perform the best. You can view this report by navigating to Journey Orchestrator > Program Analytics > select Customer Analytics > Email Template Performance Report.

2 Access to new Email Template Performance Report.png

The report includes an entry for each email template, and displays columns of performance stats calculated based on the template’s use throughout all Programs within your org. These columns are not available for reporting outside of the Email Template Performance Report in Program Analytics. The performance stats include Delivery Rate, Open Rate, Click to Open Rate, Bounced Rate, and Unsubscribed Rate. The stats are displayed as percentages with the actual number of relevant messages in parentheses. For example, under Delivery Rate the number in parentheses reflects the actual number of messages delivered, under Open Rate the number in parentheses reflects the actual number of times the mail was opened for the first time by the receiver, and so on. For more information on this report, refer to Program Analytics: Reports Across Programs.

  1. Configure Email Template HTML with more efficiency: When configuring email templates, users can auto-select text in the HTML editor based on text selected in the email template, search and replace text, and collapse style and image attributes within the HTML editor.
    1. Auto-Select HTML Text: After highlighting the text you would like to edit, click the edit HTML option to automatically navigate to that text in the HTML editor.

3 email template enhancement_edit HTML.gif

  1. Search and Replace Text: Within the email template HTML editor, press Ctrl-F to pull up the text search bar, enter the text you are searching for, and click the + icon to enter the text you would like to replace it with. You can select to replace either the highlighted text, or every instance of the text in the template.

4 email template enhancement_search and replace text.gif

  1. Collapse Style and Image Attributes: Within the email template HTML editor, click the gear icon in the upper-right corner. You can select Fold style/src to collapse all style and image attributes in the template’s HTML, and Unfold style/src to expand all style and image attributes. When the attributes are collapsed, you can click the purple collapse icon in the HTML to expand the individual element.

5.19 email template enhancement_collapse styles.gif

     For more information on editing Email Templates, refer to Create Journey Orchestrator Email Templates.

  1. Use CTA Status for Previous Step conditions in Conditional Wait: While configuring the Conditional Wait step, Admins can now select “Create CTA” as a condition based on previous program steps. Admins can use this configuration to determine how participants move through the Program model, based on the status of a CTA created in a previous Program step. For more information on how to configure previous step conditions, refer to Programs: Conditional Wait.

    Take the following steps to add this as a condition:
    1. Navigate to Journey Orchestrator > Programs and either open an existing Program, or create a new one of any model. The model will need to be configured to have a Conditional Wait step after a Create CTA step. For more information on how to configure Program models, refer to Configure Model and Emails for Programs.
    2. Click to configure the Conditional Wait step.
    3. Click +CONDITION.
    4. Select Previous Step from the condition drop-down.
    5. Select Create CTA from the initial field drop-down.
    6. Select a CTA status value from final field drop-down.

6 Select a CTA status value from final field drop-down.png

  1. Preview Conditional Wait Steps in Programs: When configuring the Conditional Wait step, Admins can now preview how Participants will proceed from that step to the rest of the Program model. This feature can be used to test the accuracy of the step’s configuration before publishing the Program.

    To preview a Conditional Wait step, click the PREVIEW option at the top-right of the Conditional Wait configuration.

7 PREVIEW option.png

This feature will display the list of participants in the Program who are in Review, Active, or New states. If no participants are in those states, the Preview will not load, and an error message will display.

From the Conditional Wait Preview screen, users can select one participant from the list and see the following:

8 Conditional Wait Preview screen.png

1. Select the participant you would like to preview from the drop-down field.

2. Navigate to the previous participant in the participant list.

3. Navigate to the next participant in the participant list.

4. A green checkmark will display when the participant has met the configured condition.

5. A red X will display when the participant has NOT met the configured condition.

6. If there is more than one condition configured with a combination of AND/OR advanced logic, the final configured condition evaluation will be displayed, along with the final result for the participant.

Note: The Preview feature is applicable for Event, Participant, Calculated Field, and Previous Step conditions.

5. Option to sync only new participants in Programs: When syncing participants in a Program that already has participants, Admins can choose to either clear the current participant list and sync participants from all sources again, or sync only participants that are new to the existing list.
To make this selection, navigate to Journey Orchestrator > Programs > open a Program with an existing participant list > navigate to the participant configuration screen > click the participant sync option.

9 participant sync option.png      The following message will display: “This will clear and sync all participants from the sources again. Do you wish to continue?”
      
Followed by the options YES and NO, SYNC ONLY NEW PARTICIPANTS.

10 SYNC ONLY NEW PARTICIPANTS.png

Clicking YES will clear the current participant list and sync participants from all sources again. Clicking NO, SYNC ONLY NEW PARTICIPANTS will only sync new participants to the existing participant list.

  1.  Refresh Power List sources before a Program is executed: Admins can now configure Power Lists to be refreshed automatically before an Outreach or Program is executed. This option can be found under Journey Orchestrator > Power List > either click to edit an existing power list or create a new one. Within the power list, click the checkbox labeled, “Refresh the power list before Outreach/Program execution”. This option is selected by default for newly created power lists.

11 Refresh the power list before Outreach-Program execution.png

This enhancement will not affect existing Programs by default.

If an existing Program is using a power list that has this feature selected, the following message will display in the source configuration screen:

12  source configuration screen.png

This Power List has refresh enabled before program execution. In order to apply the changes, save the below configuration. Admins will need to save the configuration to enable this feature for existing Programs.

  1.  Use Pivot tasks in Query Builder: Admins can now use pivot tasks within the Query Builder as a Program’s Participant source. Pivot tasks can reorganize and summarize selected data in an object to create a column for every data value. To select a Pivot task open a Program model and navigate to the Participants step > + SOURCE > Query Builder > +TASK > select Pivot from the drop-down.

13 select Pivot from the drop-down.png

This enhancement can help create email campaigns based on specific values contacts or companies might have in a particular field. For example, suppose you have a list of Open Cases and one of the columns is “Priority,” with values like “First Priority”, “Second Priority”, etc. You can pivot this and determine for each customer how many “First Priority” cases, “Second Priority” cases, and so on, that they have. Then you could use this queried information to pull in participants as part of an Email Chain or Survey on Product Satisfaction.

Query Builder pivot tasks operate identically to pivot tasks in Bionic Rules. For more information on using pivot tasks, refer to Pivot Tasks in Bionic Rules. For more information on using the Query Builder, refer to Adding Participants to a Program.

  1. Warning messages display when Admins select Pause, Resume, or Stop a Program: When Admins select Pause, Resume, or Stop a Program from the Program Status Drop-down on the model configuration page, messages will display explaining how the selected status change will affect the Program. Admins can then select either YES or NO to confirm or cancel the status change. For more information on how to change the Program statuses, refer to Configure Model and Emails for Programs.

    Note: The ability to Pause a Program is not currently available, but we plan to add it back as part of a future release.

14 Pause a Program.png

The text of the displayed message will depend on the status selected:

  • User Clicks on Pause: "Clicking YES will pause the program and the status of the participants will be changed to Paused. Are you sure you want to continue?"
  • User Clicks on Stop: "Clicking YES will stop the program and the status of the participants will be changed to Completed. You will not be able to resume the program. Are you sure you want to continue?"
  • User Clicks on Resume: "Clicking YES will make the program active and the participants will continue in the journey. Are you sure you want to continue?"
  1. Snapshot view shows “in process” states: The Program Snapshot view now has an “in process” state to show when participants are between program steps. It is normal for Participants to spend time “in process” as background jobs related to the program take time to complete. Previously, participants that were “in process” would not be reflected in the Snapshot view. Now, an icon for “in process” participants will display between the Program’s steps in the Snapshot view. This increases the accuracy of the view.

    You can view the icon by opening a published Program with Participants “in process” and clicking the Snapshot view option in the top-right of the Program model view. The icon will be visible between the program steps where participants are being processed.

15 Snapshot view shows “in process” states.png

You can click the “in process” icon to view the list of Participants currently being processed at that point in the program journey.

16 snapshot enhancement processing stage.gif

For more information on the Program snapshot view, refer to Configure Model and Email for Programs.

  1.  Use Report Builder to Query for Failed Participants: Admins can now create reports on failed participant data in Report Builder to see failure reasons for participants across all Programs. To create a report on this data, navigate to Administration > Report Builder and select AO Failed Participants History as the source object.

    Note: Failed participant data can also be found under the AO Failed Participants source object. However, filtering is not supported for participant fields on this object.

17 AO Failed Participants source object.png

  1. Program Performance Enhancements: With this release, we have completed major enhancements to our Program infrastructure which reduces the amount of time for Participants Sync and publishing Programs. With these changes, Program actions like Send Email, Create CTA, and Conditional Wait Evaluation will be performed in dedicated servers, which will drastically reduce the total time of the Program lifecycle. See the stats documented below which reflect this reduction in processing time.

#Participants

Before

Total Time Taken to Publish (HH:MM:SS)

After

Total Time Taken to Publish (HH:MM:SS)

%Decrease

Before

Time Taken to Sync Participants (HH:MM:SS)

After

Time Taken to Sync Participants (HH:MM:SS)

%Decrease

Before

Time Taken to Perform All Actions(HH:MM:SS)

After

Time Taken to Perform All Actions(HH:MM:SS)

%Decrease

10K

2:15:00

0:59:16

56%

0:15:12

0:02:00

86%

7:30:00

0:59:16

86%

1 lakh

13:32:46 PM

3:00:00

78%

1:00:20

0:05:22

91%

~24:00:00

08:03:2

67%

Additionally, with these changes we have fixed some minor issues for Program Snapshot. As a result, the participant counts for this feature are now more accurate. We’ve also added new Snapshot icons to provide a more complete picture of the currently running participants.

Surveys 2.0

  1. Use Question Library to edit and delete stored survey questions: Admins can now edit and delete existing questions they have added to the question library. For more information on creating and editing survey questions, refer to Survey 2.0 Design.

    To access the Question Library, navigate to Surveys 2.0 (Beta) > Library. The Surveys 2.0 (Beta) tab now has a chevron on the left to show options for the Library and Survey List.

18 Library and Survey List.png

Within the Question Library, admins can view the following:

19 Within the Question Library.png

  1. Chevron menu: Click this to select navigate either to the Survey List or the Question Library.
  2. Folder list: A list of folders added to the Question Library. The number of questions the folder contains is displayed next to the folder name in parentheses. Click the folder name to display the list of questions contained. Hovering on the folder also gives you the option to edit its name or delete it. Note: The Uncategorized folder can not be edited or deleted.
  3. Selected Folder: The name of the selected folder is displayed with a list of the contained questions below it.
  4. Survey Question: You can select answers for each question as a way to test how a recipient can interact with it. Hover on a question to see the option to edit it. Refer to Edit Questions in the Library for more information on editing linked questions. Click the survey question to select it. More than one question can be selected at once. When a question is selected, clicking the Action Button will give you the option to clone, delete, or move the question(s) to a different folder.
  5. Search bar: Type the name of a question to search for it in the selected folder.
  6. Action Button: Clicking this button gives the following options:
  • When no question is selected:
    • Add a new survey question to the Library.
    • Add a new folder to the Library.

20 Add a new survey question to the Library.png​​​​​​

  • When one or more questions are selected.
    • Delete: Deletes the selected question(s). Refer to Delete Questions in the Library for more information on deleting linked questions.
    • Move to folder: Move the selected question(s) to an existing folder in the Library, or create a new folder to move the question to.
    • Clone question: Creates a copy of the selected question(s) within the same Library folder.

21 Delete Questions in the Library.png

  • Edit Questions in the Library: When editing a question in the library, if the question is currently in use within a survey, you will be given the following options:

    • Update question in library and save the changes made to it in Active and Draft surveys.
    • Update question in library and save the changes made to it in Draft surveys, but Unlink it from Active surveys.

    Note: If the question is not being used in a survey, then the question modifications are saved.

22 Edit Questions in the Library.png

  • Delete questions in the Library: When deleting a question in the library, you will have two options:

    • Delete question from library and unlink it in both Active and Draft surveys: This option will delete the question from the library but unlinked versions of the question will still exist in surveys using it.

    • Delete question from library and unlink it in the Active surveys, but delete it from the Draft surveys: This option will delete the question in the library and in draft surveys. The question will remain in Active surveys and responses will remain intact.

Note: If the question is not being used in a survey, you will receive a prompt asking to confirm the deletion.

23 Delete questions in the Library.png

  1. Ability to filter Response Statistics report (renamed to Survey Statistics): The pre-built Surveys 2.0 Analytics report Response Statistics is renamed to Survey Statistics. You can view this report by navigating to Surveys 2.0 (Beta) > Open an existing survey > ANALYZE > Survey StatisticsSnip20181015_40.png

You can also filter each column of the Participants Chart that displays as part of the report. 

Survey_2_0__Beta____Salesforce_-_Enterprise_Edition.jpg

The applied filters will be honored by the report’s export feature. To learn more about this report, refer to Surveys 2.0 Analytics.

3. Survey Flattening Reports available for Surveys 2.0: By default, survey response data is spread out among several objects. Survey Flattening places this information into a single MDA object formatted with survey respondents in rows and each question in its own column to allow for easy reporting and insights into survey data. For more information on Survey Flattening, refer to Survey Flattening Overview.

24 Survey Flattening Reports available for Surveys 2.0.png

This feature is now enabled by default for all surveys in Surveys 2.0. An object containing response data for the survey will be created after the survey receives its first response. To create a report on a flattened survey object, navigate to Administration > Report Builder, and select the object with the same name as your survey. For more information on options available for reports, refer to How to Build Basic Reports.

Reporting

  1.  Pivot enhancement in Reports: Previously, pivot on reports used to happen on the UI (on the already presented data). But, with this enhancement, Admins can now pivot reports on the entire dataset from the server-side.

    Note: The maximum number of pivoted columns visible in a report are 53.

    Use Case: For example, when you create a report on Pageviews and pivot by Date, previously, the pivot was applied only to the Accounts presented in the UI, but now, pivot is applied across all of the accounts in the entire dataset.

25 Pivot Function.gif

Limitations:

  • Pivoting on SFDC objects, and the following MDA objects: Email Logs, Email Raw Events and Unsubscribed Emails will work as it was working previously.
  • You cannot Pivot the reports on which ranking is applied.
  • You cannot apply Ranking on pivoted reports.
  1. Hierarchy of Objects and Fields is visible in Show me and By Search: In the search menus for Show me and By, we now display the hierarchy of Objects and Fields using dotted lines.

26 Dotted Lines Gif.gif

  1. Widget Drill Down: You can now drill down on any point in a Widget to see a tabular list of the data associated with that report. Once you are in the drill down, you can click on the three dots to see a list of available fields to add or remove from the table. Click Apply once you have made your selections. The drill down table will display your selections when you click on a data point in the Widget.

27 WIdget Drilldown.gif

  1.  UX Improvement in Ranking: UX in Ranking offers a better user experience. Previously, when you clicked X in the top right corner of the Ranking window, it removed/cleared the previously applied Ranking. But now, when you click X, it closes the Ranking window and when you click CLEAR, it removes the previously applied "Ranking".

28 Ranking.gif

Scorecard 2.0

  1.  Collapse all groups option: Gainsight has introduced a new option to expand or collapse measure groups for a Scorecard on the C360 page. By default, all of the measure groups are expanded when you visit the C360 page. Now you can select the Collapse all groups checkbox, to collapse all of the measure groups. When the measure groups are collapsed, you can only view the health score for the whole measure group. To view scores for individual measures, you can clear the Collapse all groups checkbox. This expands all of the measure groups. You can also expand a particular measure group by using the + icon, for the required group.  

29 Collapse all groups option.gif

When you use the Collapse all groups option (select or clear the checkbox) and navigate to some other Gainsight page and return to C360 page, your configuration remains unaltered. For instance, If you collapsed all the measure groups and navigated to another page, the measure groups remain collapsed when you return to the Scorecard 2.0 section on C360 page. This applies to all customers and not just for the individual customer whose measure group was collapsed.

30  individual customer whose measure group was collapsed.gif

  1.  Modification to Auto Save functionality: Previously, when you entered comments for an individual measure and navigated (mouse over) outside the comments section, your comments were saved automatically. Now, when you enter comments for an individual measure, a mouse click anywhere outside the comments section autosaves your comments.

31 Modification to Auto Save functionality.gif

Rules Engine.

  1. New Rule Filters: Gainsight is introducing four new options to filter rules. The new filter options are:
  • Created Date: You can use this option to filter the rules based on the date of their creation. This option provides you with following seven matching criteria to filter the rule:

    • Last Month: This criteria displays all the rules which were created in the last month.
    • Last N days: In this criteria, you can enter a numerical value between 1 and 5000. The rules created from the specified day until today, are displayed. For instance, consider today’s date to be 1 Oct. 2018. if you enter 365, rules created between 2 Oct 2017 to 1 Oct 2018, are displayed.
    • Last Week: This criteria displays all the rules which were created in the last week.
    • This Month: This criteria displays all the rules which were created in the current month.
    • This Week: This criteria displays all the rules which were created in the current Week.
    • Today: This criteria displays all the rules created today; after 12 am and before 11:59 pm.
    • Yesterday: This criteria displays all the rules created yesterday; before 12 am today and after 12 am yesterday.

  Notes:

  • Definition of a Month is 1st of any month to last day of the month. (Ex: 1st Jan to 31st Jan)
  • Definition of a Week is Sunday to Saturday of any week.

32 Created Date.gif

  • Last Updated Date: You can use this option to filter the rules based on the date on which they were last updated. This option provides you with the following seven matching criteria to filter the rule:
    • Last Month: This criteria displays all the rules which were created in the last month.
    • Last Month: This criteria displays all the rules which were updated in the last month.
    • Last N days: In this criteria, you can enter a numerical value between 1 and 5000. The rules which were last updated from the specified day until today, are displayed. For instance, consider today’s date to be 1 Oct. 2018. if you enter 365, rules updated between 2 Oct 2017 to 1 Oct 2018, are displayed.
    • Last Week: This criteria displays all the rules in which the latest  updates were made in the last week.
    • This Month: This criteria displays all the rules which were last updated in the current month.
    • This Week: This criteria displays all the rules which were last updated in the current Week.
    • Today: This criteria displays all the rules updated today; after 12 am and before 11.59 pm.
    • Yesterday: This criteria displays all the rules updated yesterday; before 12 am today and after 12 am yesterday.
  •  Execution Type: You can use this option to filter rules based on their execution schedules. This option provides you with the following three criteria to filter rules:

    • Event: This criteria displays all the rules which have the Schedule type field set to Event, in the Schedule page.
    • Scheduled: This criteria displays all the rules which have the Schedule type field set to either Basic or Advanced, in the Rule Schedule page.  
    • None: This criteria displays all the rules which have not been scheduled and which are executed manually with the RUN NOW option.
  • Rule Chain: You can use this option to filter rules which are part of rule chains. The matching criteria for this option is dynamic and vary based on the following details:

    • If you have not created any Rule Chain, then you can only view one matching criteria; None. This is because none of your rules are part of any Rule Chain.

33 Rule Chain.gif

  • When you create Rule chains, you can find the names of your rule chain, appearing as matching criteria. You can select the required Rule Chain and rules which are part of the selected Chain are displayed. If you have created a Rule chain, but not added any rules to it, the Rule Chain is not displayed as a matching criteria.

34 Rule Chain is not displayed as a matching criteria.gif

  • If all of your rules are part of some Rule Chain, the None matching criteria is not displayed.

35 None matching criteria is not displayed.gif

2. Enhancements in the S3 Dataset Task

  • Ability to edit the “S3 File Configuration” section in S3 Dataset task: You can now edit the S3 file configuration section. Previously, this section was not editable once the S3 dataset task was saved. To make changes in the S3 File Configuration:
  1. Click the EDIT button.
  2. You can change the csv/tsv file, switch to another S3 bucket or make any other changes in the S3 File configuration.
  3. Click Load Column Details when you are done with your changes. The fields in the Columns section are automatically updated based on the columns in the new csv/tsv file.
  4. Click SAVE to save changes in the latest S3 File Configuration.

36 Edit S3 Config..gif

IMPORTANT

  • If you make changes to an S3 dataset task before Rule execution starts, the rule is executed successfully.
  • If you make changes to the S3 File Configuration section during Rule execution, execution fails at that point. Records which were processed before the changes, remain intact. But no further records are processed after you change the csv/tsv file or S3 bucket. To learn more about how to view successfully ingested records and records which are failed to ingest, refer the enhancement “Partial Success” Execution Status for S3 dataset.
  • If you make changes to the S3 File Configuration section when the rule  execution has just started or is in the execution queue, system displays an error message stating that file not found or Bucket not found, based on the changes made. The rule execution fails.
  • Once you ingest data through S3 dataset, you can create an Action on the Rule to load data. If a csv/tsv file column is part of Rule Action and you wish to delete this column, from the Columns section, the system sends an error message. You must first remove the required column from the Rule Action page and then remove it from the Columns section of the S3 Dataset task.
  • “Partial Success” Execution Status for S3 dataset: During the rule execution using an S3 dataset task, if some records fail to ingest due to any reason, rule is executed partially and status appears as Partial Success in the Execution History.

    In a Partial Success rule, you can find two downloadable files for the S3 dataset. The first download link (grey in colour) contains the file that has records which were successfully ingested. The second download link (red in colour) contains the file that has records which failed to ingest. When you click the red download link, error csv file is downloaded and you can see the list of errors and records that are failed to ingest.

37 “Partial Success” Execution Status for S3 dataset.png

  • Automapping of Data types in column section: In an S3 dataset task after you complete configuration in the S3 File Configuration section, you can now see that the Data types between the csv/tsv headers and output columns are automatically mapped. You can check the mappings of data types and change them as required.

38 Automapping of Data types in column section.png

  • Ability to load Dropdown list items either via labels or GSID from CSV file to an S3 Dataset: If you have dropdown list items in either labels (Ex: Active, Inactive, etc.) or their corresponding GSIDs in a CSV header, system allows you to store these values in the columns of an S3 dataset. You can use these values to match with dropdown list items in MDA (Ex: Company > Status) in the action types: Load to Gainsight objects.

  • Introduction of GSID data type: Previously, the Data Type column in the Columns section contained five data types. Now the sixth Data Type GSID has been introduced. Previously, GSID fields were mapped as String data types. Now these can directly be mapped as fields of GSID Data type.

39 Introduction of GSID data type.png

  • Enhanced Support for Date and DateTime formats: Previously, only a few Date and DateTime formats were supported in an S3 Dataset task. Support has been extended to include many more Date and Datetime formats.

40 Enhanced Support for Date and DateTime formats.png

The list of newly supported Date formats is given below (Click here to expand the list):
yyyy/MM/dd
M-dd-yyyy
M-dd-yyyy
MM-d-yyyy
MM/d/yyyy
MM-d-yy
MM/d/yy
M-d-yy
 
The list of newly supported DateTime formats is given below (Click here to expand the list):
M-d-yy HH:mm
M-d-yyyy HH:mm
HH:mm
M-dd-yy HH:mm
M-dd-yyyy HH:mm
HH:mm
M/d/yy HH:mm
M/d/yyyy HH:mm
M/dd/yy HH:mm
M/dd/yyyy HH:mm
MM-d-yy HH:mm
HH:mm
MM-d-yyyy HH:mm
MM-dd-yy HH:mm
MM-dd-yyyy HH:mm
HH:mm
MM-dd-yyyy HH:mm:ss
MM/d/yy HH:mm
MM/d/yyyy HH:mm
MM/dd/yy HH:mm
MM/dd/yyyy HH:mm
MM/dd/yyyy HH:mm
MM/dd/yyyy HH:mm:ss
yyyy-MM-dd HH-mm-ss
yyyy-MM-dd HH:mm:ss
yyyy-MM-dd HH:mm:ss.S
yyyy-MM-dd HH:mm:ssZ
yyyy-MM-dd'T'HH:mm:ss.SSS'Z'
yyyy-MM-dd'T'HH:mm:ss.SSSZ
yyyy-MM-dd'T'HH:mm:ss.SSS
yyyy-MM-dd'T'HH:mm:ssz
yyyy-MM-dd'T'HH:mm:ssZ
yyyy-MM-dd:HH-mm-ss
 

3. Formula Fields enhancements

  • Rule Date Function in Formula Field: A new function called Rule Date has been added to the Date Formulas. This function returns the Date on which the rule is being executed. This function does not accept any arguments. This function provides you the capability to directly use the current date as a new column.

41 Rule Date Function in Formula Field.gif

  • community-icon.png Support for negative results in Date Diff function: Date Diff function subtracts the start datetime field value from the end datetime field and it returns the difference in number of days. Previously, even if the end datetime field had a lower value than start datetime field, the result (number of days) was converted to a positive value. Now, the Get Signed Value checkbox is introduced. If you select this checkbox, negative values are not converted to positive values in the result.

42 Support for negative results in Date Diff function.png

For example, if your start datetime value is 5 Jan 2018 and end datetime value is 2 Jan 2018, Date Diff function subtracts start datetime from end datetime. So in this case, the output would be -3 days. Previously, this negative value was converted to a positive value and the output was displayed as 3 days. However, now if you select the Get signed value checkbox, the negative value is returned as -3.  

DateDiff Negative value.png

 

  • Ability to use Rule Date in “end datetime” field of Date Diff function: You can now use the Rule Date (current date) in the end datetime (minuend) field of the Date Diff function. Previously, only the Date and Datetime data type fields in the Show section of the dataset could be used as arguments in Date Diff function. Now you can use Rule Date as the minuend of this function, from which the subtrahend start datetime would be subtracted and the difference is returned in number of days.

    In the image below, Closed Date and Created Date are displayed because they are used in the Show section of the Source dataset; MyCTAs. However, Rule Date is not part of the source dataset. But as a result of this enhancement, Rule Date is displayed in the end datetime field.

43 Ruledate-datediff.gif

4. Pause and Resume capabilities in Rule Schedule:

  • community-icon.png Rule Schedule pause: Previously, if a rule execution fails, the rule moved to the inactive state and any schedule associated with the rule was deleted.

    Now, if a rule becomes inactive due to either:
    • execution failure
    • Abrupt interruption
    • Rule status is changed manually, 

the schedule associated with the rule is not deleted. The schedule is paused. Once you make the rule active again, the schedule associated with the rule also becomes active.

Note: If your Rule schedule type was set to Event, the event is deleted, if the rule execution fails. Rule Schedule is paused only when Schedule type is either Basic or Advanced.

Rule Schedule pause.gif

  • community-icon.png State preservation for cloned rules: Now if you clone an active rule, the cloned rule is also active by default. Similarly when you clone an inactive rule, the cloned rule is also inactive. After a rule is cloned, schedule of the source rule is not applied to the target rule. You must schedule it manually.

    In the below image you can see that the Source Rule Account Rule has a schedule (10/1/2018 12.00am) and is active. However, the cloned rule Copy of Account rule is active, but does not have a schedule.

45 Rule Clone.gif

Gainsight Data Management

  1. Changes in the On Delete option in Person Object Model: On Delete option in the Company ID field in the Company Person object is changed to Delete from None. This enables deleting a record from the Company Person object automatically when the associated record in the Company object is deleted. To see this enhancement:

    1. Navigate to Administration > Data Management and click Company Person object to check the schema
    2. Select Company Person object > select Company ID field

Similarly, On Delete option in the Relationship ID, Relationship Type ID, Company ID, and Company Person ID fields in the Relationship Person object is changed to Delete from None. This enables deleting a record from the Relationship Person object automatically when the associated record in either Relationship, Relationship Type, Company, or Company Person object is deleted.

Note: You cannot change On Delete option in the above fields from Delete.

46 Changes in the On Delete option in Person Object Model.png

You can manually delete details of a person from the C360 > Person section. This in fact deletes attributes of a person in association with a Company from the Company Person object. For more information, refer enhancement in the C360 section.

C360/R360

  1. community-icon.png Delete records in Company Person Object from C360 page: You can now delete a record from the Person section in the C360 page. This operation deletes a record from the Company Person object. This functionality works based on the same concept as used in the Object Graph. When you delete a record from the Person section in the C360 page, any other field with a lookup to Company Person object will honour the Enable lookup > On Delete option used in the target field.

    Following are the impacts after deleting a record from the Person section in the C360 page:
  • Record is deleted only from Company Person Object.
  • The corresponding record in the Relationship Person Object is also deleted.
  • Master person record is not deleted from the Person Object


To delete a record from the Person section of the C360 page:

  1. Navigate to the C360 > Person section.
  2. Click the delete button of any record.

46 Delete Record.gif

Connectors 2.0

  1. Gainsight API in the Connectors 2.0 page: A new connector called Gainsight API is introduced in the Connectors 2.0 page to generate a unique Gainsight Access Key instantly. This access key is used for authentication to pass in the request header “Accesskey” for all of your API requests into Gainsight.

    You can create only one Access Key per tenant and it does not expire. You can reset the existing access key anytime, but the new access key should be replaced in headers of all future API requests.

    To create a unique Access Key:
    1. Navigate to Administration > Connectors 2.0 > [Click Gainsight API].
    2. Click the Create Connection button and click GENERATE ACCESS KEY.

50 Gainsight API.gif

  1. A new Access Key is generated that you can copy and use as an authentication for all of your API requests into Gainsight.

51 new Access Key .png

  1. Click RESET ACCESS KEY to reset the existing access key anytime later.

    Note: New access key should be replaced in headers of all future API requests.

X-Org Migration

  1.  New Dropdown Data Types can now be migrated through X-Org Migration Tool: Picklist/Multipicklist under Schema (Both Standard and Custom), and URL Datatype can now be migrated using the X-Org Tool. For more information about how to migrate Single Select and Multi Select Picklist, refer to the Corss-Org Migration article.

  2. WhoID/WhatID data types can now be migrated through X-Org Migration Tool: Cross Org can now migrate reports built on top of MDA objects with WhoID/WhatID/Record ID data type as a field. For more information about how to migrate WhoID data types, refer to the Corss-Org Migration article.

  1. Record ID data types can now be migrated through X-Org Migration Tool: Cross Org can now migrate Record ID data type. Both Source and target orgs must have the same Record type. This should be considered as a prerequisite in order to perform the migration. For more information about how to migrate Record ID data types, refer to the Corss-Org Migration article.

  2. X-Org is enhanced to support Bulk Insert for Schema and Meta: You can now migrate multiple or all schema and meta using X-Org migration tool. When Bulk insert is used for migrating Schema/Meta:

    1. Navigate to Administration > MIGRATE > New Migration.
    2. Provide the username and password of the target org where you want your schema and metadata to be migrated.
    3. Click AUTHENTICATE.
    4. Click CLOSE to access the MDA Schema screen.
    5. Select the check box beside the Source Object header. The following message appears on the screen. Click OK to continue.

  1. Click NEXT to go to Meta Data Screen where you select the checkbox beside the Categories header. The following message appears.

  2. Click NEXT twice to get to the Migrate screen where you name the migration job.

  3. Click MIGRATE.

  1. Successfully migrate bucket details for Rules which have an S3 dataset: Now if you migrate a Rule with an S3 dataset task, the bucket details are also migrated successfully. Previously, when you migrated rules with S3 dataset tasks:

  • Only the rule was migrated successfully; the associated S3 bucket was not migrated.
  • The S3 Bucket field on the S3 file configuration section showed None and was disabled. This phenomenon occurred irrespective of whether a Gainsight Managed bucket or custom bucket was used in the rule.

However, now when you migrate a Rule with an S3 Dataset:

  • The rule and the associated S3 bucket (Gainsight Managed or Custom) are successfully migrated.
  • The bucket associated with an S3 dataset task, is migrated as an independent asset. You can view this asset on the Assets page of the Migration process screen.

  • A corresponding bucket with the same name as in source org is created in the target org. However, if the target org already has a bucket with the same name as in the source org, a new bucket will not be created.
  • When a new bucket is created in the target org, the associated Access Key and Security Token are not copied from the source org.
  • You must go to the Connectors 2.0 page and update the Access Key and Security Token for the bucket which was created due to migration.

Timeline

  1.  Keyboard support while selecting Attendees, Accounts and Relationships in Global Timeline: When creating an activity and adding Internal/External Recipients or Attendees in Timeline Activities, you can now select the desired recipient’s/attendee’s name from the given list of options by using the arrow keys > Enter on the keyboard. You are no longer required to switch to mouse/trackpad for selecting.

51internal-external attendees select.gif

The same enhancement can also be used while selecting Account or Relationship in the Global Timeline.

52timeline-keyboard support.gif

Permission Sets Added in 5.18 Patch Release

Gainsight introduced a new permission set called Gainsight Viewer. This permission set is designed to restrict users from editing data in the Gainsight widgets on the Account and Opportunity pages. When a user is assigned the Gainsight Viewer permission set, user cannot modify any data on the Gainsight widget (with the exception of Timeline). For more information, refer to Gainsight Viewer Permission Set.

Issues Addressed

Cockpit

  •  Custom lookup field on CTA with Account shows the account name by default: Previously, the custom lookup fields on Call to Action with Account were displaying only the account name by default, and it was not possible to select the custom lookup value from Cockpit. But now, you will be able to search and select the account values for non GS fields in CTA detail view and Customers tab, and for Linked Objects, on Admin > CTA, you will be able to search and select the account value for non default Account fields.

  • Created date of an Objective in Gantt chart is showing 1 day earlier: Previously, when you create an objective for a Success Plan, the created date of the objective on the Gantt Chart graph displays a day earlier, but when you hover over the graph, the message displays the correct date. This issue is resolved and you can now see the correct date.

  • Unable to share Success Plan when it has special character (single quote) in the name: Previously, when you shared a Success Plan with a special character in its name, it throws an error. This issue is now resolved.

  • Due date in objectives being shown as overdue in Success Slan after accessing the shared link: Previously, Success Plans with future objective task due dates are shown as overdue after sharing the link with the users. This issue is now resolved.

  • Success Plan: Checking off tasks via Gantt Chart is not closing tasks with Custom Status: Previously, when you marked a task as Completed, in the Objectives tab, the task status is not reflected in the Gantt Chart. This issue was occurring only when a custom status was used. This issue is resolved and fixed now.

  • Number fields are not populating commas in email assist templates: Email assist tasks that were not rendering the comma values for number fields in the template is now fixed.

  •  In Playbooks, when you set task due date as "CTA due date - 0 days", due date gets wiped out in Edit Mode: Previously, in playbooks, when you set the task due date as “CTA due date - 0 days” and save it, and edit the same task again, you will see that the due date section is wiped out. This issue has been resolved now.

  • Inappropriate error message when sending emails from Cockpit Email Assist: Previously, when you send an email assist, the system fails to send the email and throws an error "Fail to send email via 3rd party". This issue is now resolved.

  • Errors on deactivation of CTA Type (RISK) under Relationship which is NOT default under Account/Relationship: Previously, when you try deactivating the CTA Type (Risk) from Admin > Calls to Action > Relationship tab, which is not default type in Account/Relationship, the system fails to deactivate and throws an error “Default value cannot be deactivated", but the same can be deactivated from Admin > Calls to Action > Account tab. This issue has been resolved now.

  • Usability issue while mapping the values to the tokens in the email templates on Cockpit > Playbook >Task of Email Type: Previously, email templates with large content, and tokens set at the bottom of the template did not allow the users to choose the values at ease, as the token symbol keeps moving while assigning the value to the token. This issue has been resolved now.  

  • Email Last opened data is always being shown as NA in task detail view GE-26056: Previously, in email assist, the task detail view always displays the Email Last Opened On as NA. This issue is now resolved and displays the correct data.

  • Validate Email Task in C360 Pops up an error message when Playbook includes a Report of User Adoption: Previously, when you validate email tasks in a CTA from C360 page, system throws an error “Invalid Service Name”, this was happening only when a playbook includes a report of User Adoption. This issue is resolved, and you can now validate your email tasks from C360 page.

  • Cannot scroll the Success Criteria section when SP is in Preview mode: Previously, while sharing success plans, you were unable to scroll the Success Criteria section, when the success plan is in Preview mode. This issue is now resolved.

  • While sharing a success plan, Category column values under Objectives are not displaying properly:  Previously, while sharing success plans, the Category values under the Objectives are not displayed properly, when the category values have long text. This issue is now fixed.   

  • Success Plans RE: comments are not propagating into collaboration for the first run: Previously, when you setup a rule to create a success plan, the comments from the rule were not propagating to the Collaboration tab in Success Plans. This issue is now fixed.

  • Account name field in CTA relationship view are displayed with HTML anchor tags: Previously, in a CTA detail view, when you try editing the fields in the Relationship layout, the Account name field appears in HTML format. This issue is now resolved.

  • Preview and send is not resolving the tokens when a paragraph from email body is deleted: Previously, when you delete a paragraph from the email body, the available paragraphs doesn’t resolve the tokens when you click PREVIEW AND PROCEED. This issue is resolved now.  

  • Direct lookup fields are not populated in rules additional fields section dropdown: Previously, once you create a custom lookup field on Call to Action object and configured the same on CTA layout, an issue occurred while using it in Rules Engine.  When using the "Call To Action" Action Type, the newly created lookup fields were not displayed in the Additional fields > Default group section. This issue is resolved and you could now see the direct lookup fields in the default group section.    

  • Filters are not honored in Success Plan type layout configuration when Field mapping is used: Previously, when you use Field Mappings in Success Plan Type layout configuration, filters were not working when field to field filters are applied. This issue is now resolved.

Reporting

  • SP Export: Time locale is not being honored: Previously, when you export a Success Plan as snapshot, the user Time Locale was not being honored. This issue has been resolved now and you can see the user Time Locale in the exported snapshot.

  •  Issue in the Reporting on User Shared Detail object: When you tried to generate a Report on User Shared Detail object and added lookup fields, it did not show values from lookup object and GSIDs instead. This issue is resolved now and you can see values from lookup object if you add lookup fields into the Report on User Shared Detail object.

Surveys

  • Internal Survey Responses not updating in real time: Previously, when a survey received an internal response, it would not update the MDA flattened object for the survey in real time. This issue is now resolved, and responses are reflected in the flattened survey object in real time as expected.

  • Powerlist execution appears successful when failing: Previously, Powerlist execution would sometimes appear to complete successfully within the UI, when it actually failed with an exception. This was caused by a formatting change. The issue is now resolved, and Powerlist execution completes successfully as expected.

Scorecards

  • Comments displayed incorrect text after an edit: Previously, in the Scorecard mass edit report, when you edited and saved the comments, the edited comment displayed incorrect text. This issue is now resolved and comments display the right text after an edit.

  • Special characters not supported in Measure name: Previously, if you used any special characters in the measure name, the measure was not saved, thus preventing you from creating the measure. This issue is now resolved and you can use special characters while naming a measure.

  • Snapshot Date field displayed incorrect date in Rule result page: Previously, when you tried to run a bionic rule with Account Scorecard History object, and used the Snapshot date field, rule results showed an error. The Snapshot date in the Execution History tab of the Rule, displayed an incorrect date. This issue is now resolved.

  • Snapshot Date field displayed future date: Previously, the Snapshot Date field displayed last date of the month, even before the month ended (Monthly Time Granularity). This issue is now resolved and the Snapshot Date displays displays last date of the month, only after the month has ended.

  • Mass edit report displayed Comments only after a page refresh: Previously, in the Scorecard mass edit report, if you added or modified comments, the updated comments were displayed only after the page was refreshed. This issue also occurred when you used any inline filter for any column on the mss edit report. This issue is now resolved and you can view edited comments without refreshing the page.

  • Scorecards displayed “No Score” on C360 page, after Migration: Previously, after you migrated from Scorecards 1.0 to Scorecards 2.0, the Scorecards 2.0 section of C360 displayed “No Score” if the Score value was zero. This issue is now resolved and the Scorecard 2.0 section displays the right score values.

  • Scorecard View on Gainsight page Fetched Limited Results: Previously, in the Scorecard view of the Gainsight page, when you tried to search for a Customer in the Customer column, the search returned only those matching records which were present in the current page. Matching records present in subsequent pages were not returned. This issue is now resolved and search is now performed on all the pages.

  • Last Modified by fields displayed incorrect Email ID for a Scorecard update rule: Previously, when you used a Bionic rule to update a Scorecard, the rule results sheet displayed Gainsight techops mail ID, instead of your Email ID. This issue is now resolved and you can find the correct mail ID in the Last modified column of the rule results sheet.

  • Scorecard trend arrow displayed an upward trend for the lowest score: Previously, the Scorecard trend arrow for a particular Account displayed an upward trend even for a score which was lowest, as compared to all other scores for that Account. This issue is now resolved and Scorecard trend arrow shows the right direction.

  • Scorecard trend arrow was not neutral even when the Current Score and Previous scores were same: Previously, the Scorecard trend arrow showed a positive or a negative trend, even when the Current Score and Previous Score fields had the same score. This issue is now resolved and the Scorecard trend arrow remains neutral if Current Score and Previous Score fields have the same value.

  • Date and Datetime fields displayed incorrect format, after modifying the Health Score: Previously, in a Scorecard mass edit report, if you modified the health score for a measure, the values in Date or Datetime data type fields was displayed in an incorrect format. This issue is now resolved and Date and DateTime fields do not display incorrect format, if modify the Score.

  • Help text not displayed in Scorecard mass edit report: Previously, when you provided some help text for grading schemes on the Configure help text window, the corresponding help text was not displayed on the Scorecard mass edit report for any of the grading schemes. This issue is now resolved and help text is displayed for every grading scheme on the Scorecard mass edit report.

  • Manual score update displayed Internal Server error: Previously, when you tried to modify the Score for a manual measure, the system displayed an error. This issue is now resolved and you can edit manual measures now.

  • Lack of support for decimal numbers in calculation of weights: Previously, when you tried to configure weights on the Configure weights page, there was an issue. If you used decimal numbers in the weights, only the whole number was considered and the fractional part was ignored, while calculating the sum of all weights. For instance if you included 3.75 in your weight, only 3 was considered, while calculating the sum of weights. This issue is now resolved and you can now use decimal numbers up to two decimal points in weights.

  • Rules loaded partial Scorecards comments: Previously, when you tried to set the score for a measure from the rule and included some comments in the rule, the rule failed to load the comments fully. Instead only some part of your comments was loaded and hence the Scorecard section of C360 also displayed partial comments. This issue is now resolved and rules fully load the comments.   

  • Unable to set scores for manual measures: Previously, when you tried to update the score for a manual measure, the screen was unresponsive thus preventing you from updating the screen. This issue is now resolved and you can update scores for manual measures.

  • Modified Score displayed date time values in UTC time zone: Previously, when you modified a score, the modification date was displayed in UTC timezone and not in your local time zone. This issue is now resolved and you can now view the modified date in your local timezone.

  • Scorecard mass edit report displayed stale scores: Previously, the Scorecard mass edit report displayed stale scores even if the validity period of the measure was still active. This issue is now resolved and stale scores are not displayed for measures with an active validity period.

  • Mass edit report displayed values of Number fields with left justification: Previously, the Scorecard mass edit report displayed the values of Number fields with a left justification. This issue is now resolved and values in Number fields are displayed with a right justification.  

  • Unable to filter data in Date, Date Time, and Boolean Data types: Previously, when you tried to filter data on the Scorecard Mass Edit report or Dashboard, for a Date, Date Time, or Boolean field, an error message was displayed which prevented you from filtering the data. This issue is now resolved and you can filter data for Date, Date Time, and Boolean fields.

C360

  • C360 Action column opened records in Classic version for a Lightning enabled org: Previously, when you tried to edit or view any record from the C360 page (Contact, Opportunity), you were redirected to the right page, but the contents were displayed in Salesforce Classic mode, even though Salesforce Classic view was disabled. This issue is now resolved and any new page accessed from the C360 page, displays data in Lightning mode, if Salesforce Classic view is disabled.

  • Account Name populated incorrectly when adding a new Sales order from C360 page: Previously, when you tried to create a new Sales Order from the Sales Order section(Related List) of the C360 page, you are navigated to the New Sales Order setup page (Salesforce). The Account Name field on this page displayed the Account ID instead of Account Name. Due to this a “No Matches found” error (Account not found) occurred and thus prevented you from creating new Sales Order. This issue is now resolved and the Account Name field displays respective account’s name and thus you can successfully create a Sales Order from C360 page.

  • Owner Id field on the Edit Attributes page was read only: Previously, when a non admin user tried to change the owner of  an Account from the Edit Attributes section in C360, the Owner ID field was freezed. This happened even after the admin granted required edit permissions to non admin users. This issue is now resolved and non admin users can now edit the Owner ID field on the Edit Attributes section of C360, if the admin has granted the required permissions.

  • Unable to perform Inline search for dropdown fields in C360: Previously, when you tried to add a value to a drop down list Edit Attributes page in C360, you could not perform an inline search within the drop down menu. This issue is now resolved and you can perform in line search in drop down lists of the Edit Attributes page.

  • Comments section in Features page narrowed in Edit mode: Previously, the Edit Features window in the Features section of C360 page had an issue. The Comments column shrinked on the Edit Features page. This issue is now resolved and the Comments column does not shrink when you edit the attributes.    

  • Formula fields displayed HTML tag: Previously, when you used a formula field, the Customers tab displayed an HTML for the formula field, instead of the value of the formula field. The Summary section of the C360 page did not show any HTML tag initially but when you hover the mouse to on the Formula field the HTML tag was displayed. This issue is now resolved and formula field displays right value and no error codes.   

  • Currency fields displayed incorrect currency format after an edit: Previously, the currency field on the Edit Attributes in C360 displayed the right currency value and currency format when loaded. However, when you edited a currency field, the new currency value displayed correctly but currency format changed automatically. (For example, if a Euro 350 was modified to Euro 400, the field displayed Dollar 400). This issue is now resolved and there is no change in the currency format, when you edit a currency field.

  • Unable to edit Account Name field: Previously, the Account Name field was freezed on the Edit Attributes page of the C360 section for a Standard user. Standard users could not edit the Account Name field even after the required permissions were granted. Only Administrators were able to edit this field. This issue is now resolved and Standard users can edit the Account Name field.

  • Unable to add attachments from C360 page: Previously, when you tried to add an attachment from the Attachments section of the C360 page, an “Insufficient Privileges” message was displayed. This prevented you from adding attachments from Attachments section of the C360 page. This issue is now resolved and you can add attachments from the C360 page.

  • Widgets on C360 page displayed inaccurate data: Previously, when you created a report widget on objects with multiple account lookups, it used to use the first account lookup by default. Now, if you have multiple Account lookups, you can configure the account lookup for widget.

  • When you added the Person in C360 Layout and navigated to C360 page, it displays an error message “Method Not Allowed”. This issue is resolved and C360 page works as expected.

Customers Tab

  • Apply Button hidden in the Modify filters page: Previously, when you used the filters option and accessed the Modify filters page and tried to apply an Advanced filter, there was an issue. If you added a filter but clicked Cancel button instead of Apply, the Apply button was not displayed, when you reopened the Modify filters page. This issue is now resolved and you can find the Apply button when you reopen the Modify filters page.

  • Formula fields with an image displayed HTML tags: Previously, when you used an image in the formula field, and used that field on the Customers page, the Customers page displayed the HTML tag for the image, rather than the image itself. This issue is now resolved and you can view the image for the Formula fields on the Customers page.

R360

  • Unable to edit Date data type fields in Attributes section: Previously, the Edit Attributes page in R360/C360 did not allow you to edit some of the date data type fields. If there were multiple date fields on the R360/C360 page, there was no issue with the first date field. However, all subsequent fields with date data type had an issue. If you tried to use the month or year drop down menu, the cursor navigated back to the first date field automatically. A workaround has now been provided which eliminates the issue.

  • “Mandatory” fields automatically turn out into read only fields: Previously, when you configured a field as Mandatory field, it automatically turned out to be a read only field in R360 page. As a workaround, instead of making the field mandatory, you must create a validation rule to ensure that the field is not null, to ensure that it can be edited from the R360 page.

  • Account lookup fields populated while creating new Contact in Lightning view: Previously, in Salesforce Lightning when you tried to create a new Contact from the R360 page, the fields which had a lookup to the Account Object, did not populate the Account fields. This issue is now resolved.

  • Issue with the “&” symbol in Dashboard widgets: Previously, if a field label had an & symbol, and if you used this field as a Widget in R360, the name was not displayed properly. (A&B corp was displayed as A &and B Corp). This issue is now resolved and fields with & are displayed properly in R360 widgets.

  • Issue while editing a Relationship: Previously, when you tried to edit a relationship, you were redirected to the incorrect attribute section. This issue is now resolved and you can now edit relationships.  

Widgets

  • Date data type fields defaulted to 1970 on Timeline tab in widget: Previously, the Date data type fields on the located on the Account widget, defaulted to 1970. You need to manually scroll up to current month. This issue is now resolved. You can now view the current month, by default for date data type fields.

Data Management

  • Unable to create an object from a CSV file having Date field: When you tried to create a custom object from a CSV file having Date field, screen got static while validation is in progress. This issue is fixed and the functionality is working as expected.

Connectors

  • When your Org is in CEST timezone, Logs in Gainsight Connect were disordered. This issue is now resolved.

Rules Engine

  • Creation of Duplicate Schedules in Advance Scheduler: When you created a Schedule in Advance Scheduler and click SAVE multiple times, duplicate schedules were created on each click. This issue is now resolved and Advance Scheduler is working now as expected.

  •  When a Custom object starts with a Special Character and if admins have executed a Bionic Rule with ‘Load to Gainsight Object’, after rule execution, Admins did not receive log email. This issue is resolved and ‘Load to Gainsight Object’ action type is working as expected.

  • Post upgrading your Gainsight Org to v5.17, the space between the buttons +ACTION, SAVE, and RUN NOW became wider. This UI issue is fixed now.

  • If you create a dataset on an MDA object by adding filter on datetime field, Preview and Actual results are not matching. This issue is resolved now.

  • In the Custom Rules Setup Rule page, you could not able to add MDA fields into the filters that has mapping to users. If any custom rule that had this configuration, you could not able to open this rule. This issue is fixed now.

  • In a custom Rule, after Rule dataset created from a Dataspace, if Admin deleted a field from this Dataspace, the rule execution failed as expected but admin did not receive the failure email notification. This issue is fixed now and admins receive failure email notification on failing a custom rule with above configuration.

  • If a Rule in a Rule chain failed due to any reason, corresponding task name did not appear in the Rule chain result email notification. This issue is fixed now and you can see task details of all the rules in the email notification.

  • When an Admin applied Pivot on a dropdown list field, after aggregation on any field created a output field of data type dropdown list only. This issue is resolved and pivot operation creates a field of required data type.

  • In a Bionic Rule, Load to SFDC/MDA object, after loading number values into the String data type fields, decimal places are automatically added to the number value. This issue is resolved now and just number values are loaded into the string data type.

  • When you executed “Load to Customers” using Bionic Rules, rule result page displayed the list of customers by filtering Account names. Due to this, the number of account records inserted or updated was incorrect as there may be duplicate account names. This issue is resolved now and the rule result page displays number of accounts inserted or updated by filtering Account IDs.

Known Issues

Cockpit

  • [Data Space] Bionic Rules: ID fields in linked Objects section are not being shown up in "Call to Action" action: When you create a data space  on any object, after being linked to a CTA Type from Admin > Calls to Action > Linked Objects, an issue occurred while using it in Rules Engine. On the Setup Action page, when using the "Call To Action" Action Type, the ID fields of the linked object were not shown in the Link to an existing “Linked Object” section.

    Resolution/Work around: Follow the below steps as a temporary work around:
  1. Navigate to Admin > Rules Engine.
  2. In the Setup Rule page, create a dataset on the object you wish to.
    Note: Ensure that you link this object to a CTA Type from Admin > Calls to Action > Linked Objects.
  3. Merge the existing dataset with the newly created dataset.
  4. In the Setup Action page, create Call to Action action type on the merged dataset, you will now see the ID fields of the linked object.

Reporting

  •  Report Builder throws error when a report is created on custom object: When you create a report on a custom object which has a lookup to standard object: Company or Relationship, and try to pull a field from another standard object: Scoring Schema Definition, Scorecard Fact etc., the report builder throws an error “Server Error Occured, Please Contact Support, Message: Internal Server Error”. This issue occurs with all the standard objects except the Company or Relationship.

    Reason: This issue occurred because a field is pulled from another standard object: Scoring Schema Definition, Scorecard Fact etc., via Company or Relationship objects.

    Resolution/Work around: Create a custom field on Company or Relationship object and load data from the field which you are trying to fetch from Standard Objects like: Scoring Schema Definition, Scorecard Fact etc. to the custom field by creating a rule. To create a rule on Company or Relationship object, click here.  

Rules Engine

  • After ‘Load to MDA object’ Rule action is executed, output field names in the excel sheet displays db names, instead of field display names.

  • When you create a dataset from Matrix Data > Company without adding a field GSID, “Only few Action types are shown in the Action Setup screen…..” message is displayed in the Setup Rule page. This message should be displayed in the Setup Action page. This issue will be resolved soon.

  • When you load dropdown list items from a CSV file into the dropdown list type field using an S3 dataset task, if the field has a default value, you should pass only default dropdown list label from the CSV file, it does not accept passing GSID of this dropdown list label. This issue will be resolved soon.

  • In a Bionic Rule Setup Action page > field mappings, after dropdown list items are mapped, Preview of these items mapping should be shown on the UI. This will be added soon.

  • When you want to setup an action on Relationship data using Bionic Rules, If there is no Relationship ID in the dataset task, none of the actions can be configured now in the Setup Action page. Instead, it should not allow to setup a few actions like Load to Milestone, Set Score 2.0 if the Relationship ID is missing in the dataset. This issue will be resolved soon.

  • Tooltip for Relationship Type does not appear in the Create/Edit Rule page in Mozilla Firefox browser. This issue will be addressed soon.

  •  When an inactive Rule is Test Run, the execution status shows success. Inactive rule should not be executed. This issue will be addressed soon.

  • Bionic Rule execution email is sent both to admin user and logged-in user. The email should be sent to only admin user. This issue will be addressed soon.

  • After you create a Bionic Rule dataset from the fields of a Dataspace, if you delete a field from the Dataspace, the rule gets executed successfully. Ideally, the rule execution should fail in this case. This issue will be resolved soon.

  • Rule list filter for Rule Chain: Rule chain filter does not display all the newly added values until you refresh or navigate again to the page. This issue will be addressed soon.

  • None value should appear in the newly added Rule Chain filter if there are Rules not part of any Rule Chain.

Data Management

  • When you create a custom field of data type DateTime in the MDA Relationship object, if you assign a default value to this field, the same value does not appear when you create a report on Relationship.

Scorecards

Unable to search data on Measure Fields: Currently, you cannot search for data on the Measure fields (columns), in the Scorecard Mass edit report. This issue will be resolved in subsequent releases.

 This symbol indicates that an enhancement originated as a customer suggestion on the Gainsight Community.

  • Was this article helpful?