February 2017: 5.5 Release
Rules Engine supports new data types in MDA: With this release, Gainsight Data Management (GDM) supports Currency, Percentage, Email, Picklist, SFDCID, and GSID data types. These new data types are also supported by the Rules Engine module. Earlier, the Percentages and Currency fields were defaulted to Number; the SFDCID and Email fields were defaulted to String; but now you can see the currency and percentage data type fields. You can also add these fields in the Show and Filters sections and map them in the Action stage. In a rule, you can also fetch fields from the standard objects like GS Company or GS User (shipped with this release).
The following image shows an example where Currency, Email, and SFDCID fields are selected.
Note: Standard objects will not be available to be used as Source in Rule setup. Admins can import the data from SFDC more frequently using Gainsight - Connect. Customers cannot load Standard objects using Rules Engine, 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
- Create Milestones for Relationships: In Rules Engine, Admins can configure rules to automate milestone creation for Relationships. The list of the milestones are now displayed for both Account and Relationship types. Relationship tokens (based on the selected Relationship type) are available while adding comments. Refer Create Milestones for Relationships in Rules Engine.
- Bionic Rules in Rules Engine: A new rule type is available in Administration > Rules Engine > + RULE > Edit Rule > Rule Type which 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 now this can be accomplished with a single bionic rule.
Data is not required to be duplicated or loaded to temporary tables to get the Account Lookup and aggregate. For more information, refer to the Getting Started with Bionic Rules.
- Bionic Rules helps you reduce the rules created and all MDA custom objects (Redshift only) created by enabling Admins to work with multiple data sets from multiple data sources; as well as process the data and perform actions.
- Also see the following Tutorials:
- Enhanced Filter Component is integrated in Bionic Rules and Custom Rules. This new improvised Filter component honors the Custom Lookup options based on the Rule/Relationship Type options chosen and shows only those values in the Filters.
- Link the ‘Linked Objects’ to CTA through Rules Engine: Previously, CSMs used to manually search for a specific record and link it in the CTA Detail View, but now with this enhancement, all CTA relevant records can be linked through Rules Engine. All Linked Objects that are linked to the CTA type will be available in the drop-down. When a linked object is selected in the drop-down, Admins can choose the field to which it should be linked from the Show fields.
- Prevent the creation of repetitive CTAs: Admins can select the Create CTA once in check box in the Create CTA action to prevent the creation of CTAs based on the timeframe selected. A separate check box will be available for separate actions.
- Include CTA ID as Identifier: In the Close CTA action, Admins can now select the CTA ID > Include in identifiers check box to validate if the CTA ID should be included in identifiers while closing CTAs.
Note: When you select the Include in identifiers check box, the Type, Source, Reason, and Set CTA status to fields will become disabled and restricts the rule to mapping only with the CTA ID field. Only CTA ID will be used as an identifier while closing the CTA.
- Close Success Plan Objective CTAs: Admins can now select the Objective option from the CTA Type drop-down list to close Objective CTAs from the Rules Engine.
If the CTA type is Objective, the Objective Category field will be visible instead of Reason, and the Survey option is disabled in the Source drop-down as shown in the following image.
- ‘Close CTA’ action for Relationships in Rules Engine: CTA types associated with relationship types are available in the CTA type drop-down. CTA status associated with the Relationship type, CTA type, Global active All, and Private All are available. CTAs of the selected Relationship type can be closed.
November 2016: 5.4 Release
- Rules metadata will be migrated to MDA. AutomatedAlertRules__c and ActionTemplates__c objects will no longer be used for storing rule definitions. All rule definitions will be migrated to MDA. If you are using these objects in any form, such as reporting, please get in touch with Gainsight Customer Support.
Note: This change will not have any impact on existing rules. You will be impacted only if you have a report configured, or a workflow configured using these objects.
October 2016: 5.3 Release
August 2016: 5.2 Release
- Enhancement: Drag-and-drop rules in a rule chain at Administration > Operations > Rules Engine > RULE CHAIN > [Edit an existing rule chain].
- Enhancement: Use Data Spaces as a data source in the rules engine by creating custom rules on Account. See Data Spaces for more information.
- Enhancement: Account Lookup field flexibility in rule creation. It is not mandatory to include the Account ID field (you can use any other field that has a lookup to Account) in Account Lookup at Administration > Operations > Rules Engine > [Create a Rule] > Setup Rule. However, you must have the selected Account Lookup present in the Show field to utilize all of the Action types while setting up actions. For example, if you have selected Account ID as account lookup, you must drag-and-drop the Account ID field in the Show field.
Only Load to MDA and Load to SFDC are available while setting up actions for a rule in the following cases:
- If the lookup field selected in Account Lookup is not present in the Show field.
- If the lookup field selected in Account Lookup has an aggregation on it in the Show field.
- If the lookup field selected in Account Lookup is incorrect and you have the correct lookup field in the Show field.
- Enhancement: Click on an existing rule at Administration > Operations > Rules Engine > Rules List to view the new preview window. Earlier we had the rule detail view to display rule details.
- Enhancement: Add fields to the Email Logs object using Data Management. Admins can add the fields and assign permissions at Administration > Operations > Rules Engine > Click the Gear icon > Permissions - Rules Load Actions > [Select Matrix Data]. However, you cannot add fields to Email Raw Events and Unsubscribed Emails objects and will no longer be available in the drop-down box.
6. Enhancement: Create Success Plans for relationships using the rules engine. For more information, refer to Creating Success Plans Using Rules Engine.
7. Enhancement: You can now load data in relationship related objects with the help of new action type Load to Relationship Related Objects. Similar to the Load to Customer action for Accounts, we can migrate relationship related data to relationship related objects. The related objects may or may not be Linked Objects.