Bionic Rules is an evolutionary enhancement to the Rules Engine. This feature helps you scale your data investment by harnessing cutting-edge technology to transform customer data into value delivered. Gainsight’s Bionic Rules Engine can perform multi-step, in-memory data processing to convert raw customer data to real-world action. Bionic Rules can perform multiple fetches and transformations in a single rule; including tasks to fetch data from multiple sources, merge, aggregate, pivot and then load to an object.
Previously, multiple objects used to be joined and flattened by a series of Custom Rules, but Bionic Rules have the capabilities to transform fetched data in various ways and execute actions within a single rule.
For more information about how Bionic Rules transform data that was fetched from multiple sources such as SFDC, MDA, and Data Spaces, refer to the Bionic Rules Task Creation tutorial.
Sample Bionic Rule High-Level Task Transformation
Bionic Rules helps you reduce the rules created and all MDA custom objects created, by enabling Admins to work with multiple data sets from multiple data sources; as well as process the data and perform actions.
The following table lists the limitations that are applicable to with all Bionic Rules:
|Maximum number of tasks allowed||10|
|Maximum number of Show fields in each task||50||In Pivot task, 200 cases can be used to pivot on a field|
|Maximum number of Group by fields in transformation tasks||5|
|Maximum number of filters allowed in each task||26||No limits in Action filters|
|Task Name length||80||Alphanumeric, _ and space are supported here|
|Task Description||200||All characters|
|Out Dataset Name||60||Alphanumeric, _ and space are supported here|
Fetch tasks support data sources from SFDC, MDA (Redshift Only), and Data Spaces.
Each field in every task can have a field label input by the user which will be used as a field alias while querying and as a header in the csv result. While querying from usage data, if any of these field aliases contains reserved keyword, you must modify the Output Field Label name before clicking SAVE, otherwise it displays an error message.
Picklist and Multipicklist includes/excludes filtering is supported with MDA.
Transform tasks include Merge, Pivot, and Aggregation.
Merge task does not support filters. Aggregation and Pivot Tasks support filters.
The following table lists various collections which are supported/not supported in Bionic Rules.
|Object Type||Supported in Bionic Rule?|
|Email RAW events||X|
|Segment Raw Collection||X|
|Mixpanel Raw Collection||X|
|GA Raw Collection||X|
|Note: Customers cannot load from Standard objects in Custom Rules but when an object in MDA is selected and that has a lookup on a standard object, the standard object will be accessible in rules. This is not supported in Bionic Rules since MDA joins is not supported.|
Following are the limits at the fetch level in Bionic Rules:
|Fetch data from||Record limits|
|Fetch data from SFDC - Largest org||6.3 million|
|Fetch data from MDA - largest dataset||2 million|
|Note: The rule will be stopped from execution if it takes more than 8 hours and it will be marked as failed. Gainsight recommends you to start with 2 million records for processing the fetch task.|
Action filter is case sensitive and it does an unresponsive check.
Rules Preview does not show the detailed information of every task present in Bionic rule. It gives basic information along with the task flow diagram.
Rules at Account level do not include the absence of data feature. It is not needed as users can create multiple tasks, merge data, and the rule will transform tasks.
At the Account level, Bionic Rules do not support the Send Email action, since CoPilot is used for this.
In Pivot, 50 measures + 200 columns are allowed on 1 Pivoted field.
Aggregation task supports date functions in Group by like Day, Week, Month, Quarter and Year.
Before you begin building Bionic Rules in Gainsight, it is helpful to know the following, or to work with your Salesforce Admin to understand:
Where is your usage data stored and how is it integrated? (Native/SFDC, Matrix/MDA, or Dataspaces)
Note: Contact Gainsight Customer Support to enable Redshift.
What is the usage data loading frequency, granularity, and data week?
weekly or monthly: will determine whether to sum/avg or max/min, and so on.
granularity: user level, instance (product) level, or account level
data week: Sun - Sat, or Mon - Sun
Additionally, you must be familiar with Salesforce and Gainsight objects, to some extent:
Salesforce objects: Most SFDC objects only contain the present state of data.
CustomerInfo object: The equivalent of the Account object; it only contains the present state of data. Purpose of CustomerInfo object in Gainsight is to assemble various customer data in one object. During implementation, Gainsight makes a mirror record if your account records on the CustomerInfo object.
Usage data object: Gainsight's usage data object contains historical data on the usage and engagement measures you choose to track, as well as weekly or monthly snapshots of your current usage data.
MDA/Matrix Data: In order to access the Data Management console, and be able to view and load data, a user must have access to the Visual Force Page JBCXM.COM.
Gainsight Objects to Field Map: Navigate to Setup > Installed packages > click JBCXM > View Components. The list of all Apex Classes, VF Pages, Objects and Fields that are part of our Managed Package will be displayed.
Bionic Rules for Account vs. Relationships
Bionic Rules can be built for both Account and Relationship levels and support actions based on the option selected.
|Call to Action ( Create or Update)||Yes||Yes|
|Call to Action (Close)||Yes||Yes|
|Load to Usage||Yes||NA|
|Load to Customers||Yes||NA|
|Load to Milestone||Yes||No|
|Load to Feature||Yes||NA|
|Set Score||Yes (only for existing customers)||No|
|Set Score 2.0||No||No|
|Load to SFDC Object||Yes||NA|
|Load to MDA Subject Area||Yes||NA|
|Load to Relationship||Yes||NA|
|Load to Relationship Related Objects||NA||Yes|
For general information on Relationships, see Relationships Overview. If you have Relationship types setup in your org, you can also create a rule for a relationship. You must select the appropriate Relationship Type from the drop-down list.
The following image shows the Relationship Type field.
Note: When you set up a Bionic Rule for Relationship Type, key fields related to a particular object are automatically added in the Show area. For example, if Relationship object is selected, Relationship ID and Relationship Account fields are automatically added in the Show section. The fields are dependent on the Relationship Setup.
The following articles walk you through the basic steps to create a Bionic Rule:
Bionic Rules - Significant Enhancements in Rules Engine
This new rule type at Administration > Rules Engine > + RULE > Edit Rule > Rule Type drop-down list helps perform multiple fetches and transformations in a single rule like fetch data from multiple sources, merge, aggregate, pivot and then load to an object.
Search Rules by name, type, action type and so on: You can now search Rules on the Administration > RULES LIST > [click on the search icon]. This shows the available Rule Type in the Choose Rule Type drop-down list from where you can select the type of rule you want to create.
Export task output to S3 Bucket: In Bionic Rules, select the Enable Export checkbox under the Export to S3 section at the Rule Setup screen.
As an Admin, you can now export each task’s output to S3 buckets which can either be Gainsight Bucket or Custom Bucket with encryption and decryption capabilities. For more information, refer to the Export to S3 from Bionic Rule article.
Admin can now provide inputs for every Show field added in each Bionic Rule task.
Note: When you create rules, it gets validated and the icon depicts that selected Output Field Label is the reserved keyword and can be used only if you rename the label.
- The human readable column headers are now visible in the UI (Preview, Actions screen,and CSV sheets). The following image shows the Preview of a sample Bionic Rule.
- Output Header is the header name displayed in the CSV Sheet that is generated post the Task Execution. You cannot change the Output Header name once it is saved for the first time to avoid conflicts in case the same field is used in other tasks; and the space will be replaced with ‘_’ automatically. This name will be used as Output Header to process actions.
Admins can validate Picklist values, CTA types, Relationship types present in rules before deletion.
Bionic Rule Preview displays basic details of tasks, including the link to download the final task output as csv.
- The tasks dependency graph (DAG) is displayed in Rule Setup tab as shown in the following image.
The action filters and transform tasks (Pivot and Aggregation tasks) in Bionic Rules provide field-to-field mapping support as well.
Bionic transformation Pivot and Aggregation tasks enable Admins to GroupBy Date and Datetime fields by applying custom functions such as Day, Week, Month, Quarter, and Year.