Automatic Updates

1.  Advanced search filters on Rules List page: In the Administration > Rules Engine page, new search filters are available. You can filter the rules in the Rules List page using the following fields:
   1. Action Name - Select a rule action name.
   2. Created By - Select the name of a user who created the rule.
   3. Last Updated By - Select the name of the user who last updated the rule.
   4. Relationship Type - Select a relationship type.
   5. Rule For - Select Account or Relationship.
   6. Rule Type - Select Bionic or Custom.
   7. Source Object - Select one or more source objects used in the rules. The source objects of all the rules will be available here for selection.
   8. Target Object - Select a target object. A target object is an object to which the rule is writing data to (all Load to actions write data to objects). You can select either one or multiple target objects.

The GIF below demonstrates an example use for Advanced Filters where Source Object =  "Case OR Milestone" AND Source Object = "Account"

For multiple options selected within the same row (A), the OR is applied within that row.  
For instances where multiple rows are added (A + B or A + B +C) the AND logic is applied between the rows.
Notes:

• You can select multiple filters from the Filters dialog.
• At a user-level, the filters will still be applied even when you refresh the page or navigate to a different page. To remove a filter, click on the X icon or click RESET and then click APPLY.
• Rule title search and Active/Inactive search is performed on the filtered list.  

2.  Support for event based triggering of rule and rule chain: You can now run a rule using an event from the Events Framework in Gainsight. In the Schedule step of a Bionic Rule, a new option is introduced for this purpose. Using the Schedule Type as Event, you can run the rule using CURL command. CURL command is a handy way to trigger a rule outside of Gainsight. In a broader sense, event-based triggering of a rule, enables you to integrate rules deeper with non-Gainsight services if you have developer support.
   1. Navigate to Administration > Rules Engine.
   2. Create and configure a Bionic Rule.
   3. Go to the Schedule step.
   4. In the Schedule Type list, select Event.
   5. Select a Topic from the list.
   6. Select an event from the list.
   7. Click SAVE. After the save is successful, the SHOW CURL COMMAND option appears.
   8. Click SHOW CURL COMMAND. The CURL command appears on the screen.
   9. Click Copy command to clipboard option.

10. Run the command in a Mac Terminal or Windows Powershell to run the rule. Once the command is executed, the rule will run instantly with the current date and time.  
    
    Limitations

• If there is a pending execution of the rule, the event-based execution will be rejected. You can find out the rejection reason in the rule’s execution history.
• Per organization, 100 event-triggered rule executions are allowed in a day (24 hour period). The 24-hour period is between 12 am in a day to the next 12am UTC.  

3.   Auto-mapping of the picklist values is now supported in the Bionic Rules > Setup Action page: When you load data from the SFDC/MDA object to MDA/SFDC object using Bionic Rules, in the Setup Action page, while performing field mappings between the Picklist type fields, picklist values are mapped automatically between the source and target fields when values are same on the both sides. Picklist values are mapped automatically based on the picklist value label in the target field. Comparison between the source and target values is case in-sensitive for auto-mapping.
   
   When there is no match found for the source picklist value in the target picklist, empty option is selected in the target picklist and you can map the target picklist value manually. To see this enhancement:
   1. Navigate to Administration > Rule Engine > Setup Action (Bionic).
   2. Create a dataset from either SFDC or MDA object.
   3. Use Action type, Load to SFDC Object or Load to MDA Subject Area. While mapping Picklist type fields, picklist values are mapped automatically between the source and target fields when the values are the same on both sides.

In the following image, Industry (Picklist) field is mapped from the MDA object to SFDC object.

4.   Re-ordering of Actions in Bionic Rules: When you set up multiple Actions on a dataset in a Bionic Rule task, you can now arrange the Actions in any order and save it. This helps to execute multiple actions in the arranged order within a Bionic Rule task.
   
   In the following example, Actions are rearranged and will be executed in the following order:
   1. Load to Customers
   2. Load to Company
   3. Call To Action

Note: As you cannot move the Actions from one task to another, you cannot re-order the Actions between multiple tasks.

5.  Create Dataset from a file in any S3 Bucket and Support Decryption on the file: You can now create a new connection for any S3 bucket and use in Bionic Rules to create a dataset by fetching files from the S3 bucket. Earlier to Gainsight version v5.14, you could fetch files from Gainsight Managed bucket only.
   
   If your csv/tsv file in the S3 bucket is encrypted, you can now apply decryption on the file with a valid PGP key from the Setup Rule page. 
   
   To create a new Connection for an S3 bucket:
   1. Navigate to Administration > Connectors 2.0.
   2. Click Create Connection. Create a Connection dialog appears.
   3. Enter the Connection Name: My S3 Custom Bucket and the credentials of your S3 bucket like Bucket Name, Access Key, and Security Token. Make sure that you enter valid credentials to establish an S3 connection.
   4. Click TEST CONNECTION to validate the S3 connection. If the credentials for S3 bucket are correct and valid, it displays the success message, Connection Successful. if not, it displays an error message, Connection failed.
   5. Click CREATE. A connection for your S3 bucket is established and the same appears in the Setup Rule page.

To create a dataset using Bionic Rules by fetching a file from an S3 bucket:

1. Navigate to Administration > Rules Engine and create a Bionic Rule.
2. In the Setup Rule page, click +TASK and select S3 Dataset.
3. In the S3 File Configuration section, you can now select your S3 bucket. Select My S3 Custom Bucket.
   Note: You can see an S3 bucket in the Setup Rule page for which you have established an S3 connection in the Connectors 2.0 page.

4. Configure the file path as Equals / testbyveera/Input/CompanyDetails-2018-04-24.csv (full file path). You can change the file path configuration as required.

5. If your csv file in the S3 bucket is encrypted, select the checkbox and select the correct PGP key to apply decryption on the csv file.
   Note: To configure a PGP key for decryption with Gainsight, contact support@gainsight.com so that you can use the same in the Setup Rule page.

6. Select the correct File Properties and click LOAD COLUMN DETAILS or PREVIEW. System reads your csv file in the S3 bucket and loads the csv columns or displays preview of records in the csv file.

For more information on the S3 Dataset configuration, refer the article S3 Dataset Task in Bionic Rules.

6.   Ability to clone an existing action in a Bionic Rule Task: You can now clone an existing action in a Bionic Rule task, modify the configurations in the cloned action, and save it. This increases efficiency and reduces the possibility of errors. The new action is added at the bottom in the current task.
   
   To clone an existing action:
   1. Navigate to Administration > Rules Engine.
   2. Set up a Bionic Rule task with multiple actions.
   3. In an existing action, click the Clone button. Existing action is cloned and added at the bottom in the current task.
   4. Make the required changes in the new action and click SAVE.

7.  Support of new Date formats in the S3 Dataset task: New Date formats are added to the Date Configuration section in the S3 Dataset Task configuration. This enhancement helps in supporting different date formats in the csv/tsv records while creating an S3 Dataset task. For more information, refer S3 Dataset Task in Bionic Rules.

8.   Auto-population of Rule Date and logged-in user Email Id in the Run Rule dialog: When you click RUN NOW to trigger any Bionic Rule, Rule Date (today) and the logged-in user Email Id for sending rule result are auto populated in the Run Rule dialog.
   
   Note: You can add more Email Ids to send a copy of the rule result.

Automatic Updates

1.  Integration with Survey 2.0 for the Generic, CSAT, and NPS® models: Surveys built in Surveys 2.0 can be selected when configuring survey models from the survey drop-down.

Note: Only the Generic model supports the Anonymous and Semi-Anonymous options with Surveys 2.0.

Incremental Improvements

1.  New actions available for Enhanced Advanced Outreach models: Survey models now have a Responded step that creates branching options based on whether or not a participant has responded. Each branching option can be configured with new actions such as Conditional Wait, Wait Timer, Send Email, Create CTA, and End Outreach. This is available for the Generic, NPS®, and CSAT survey models. This increases the flexibility of the models. They can be extended to 43 steps compared to 9 before. These new actions are compatible with both Surveys 1.0 and 2.0. For more information on configuring these steps, refer to Configure Models for Advanced Outreach.