Custom Rule Retirement FAQs

When will I no longer be able to create new Custom Rules? 

As of the October 2018 v5.19 release, you will only be allowed to create new Bionic Rules.

Will my existing Custom Rules still run? 

Yes, Gainsight will migrate the existing active Custom Rules to Bionic Rules automatically after the v6.29 release (Effective from November 9, 2021).

Are you going to disable my Custom Rules at some future date? 

Yes, but not until we have migrated your existing Custom Rules to Bionic Rules. After that, we will delete all Custom Rules after the v6.29 release.

Do I have to convert my Custom Rules to Bionic Rules now? 

After the v6.29 release, Gainsight will:

• Migrate the existing active Custom Rules to Bionic Rules automatically.

• Delete Custom Rules which have not run in the year 2021.

• Send an email notification to customers regarding the results of the migration.

What resources are available to help teach me to use Bionic Rules? 

Please see this series of articles for assistance in creating Bionic Rules. 

Will you continue to make enhancements or bug fixes to Custom Rules? 

No

Will I get any information regarding the migration result? 

Yes, Gainsight will send an email notification to customers regarding the results of the migration.

What are the advantages of switching to Bionic Rules? 

Bionic Rules offer extended capabilities including transforming, aggregating, pivoting, and merging data, as well as reading from S3. With Bionic Rules, there is no need to create multiple rules for different source objects if they solve the same business problem. This can be accomplished in just one Bionic Rule. And having fewer rules means it is easier for Admins to manage their rules overall.

Can Bionic Rules do everything that Custom Rules can do? (ie. Do they have feature parity?) 

As of the July v5.16 release, Bionic Rules will have full feature parity with Custom Rules. The 5.16 release addresses a few calculated fields scenarios that previously were not supported in Bionic Rules. Additionally, Bionic Rules can accomplish much more than was possible with Custom Rules, or that required multiple Custom Rules. 

How can I identify an absence of data for my accounts in Bionic Rules? 

Refer to the Absence of Data tutorial for detailed instructions on how to fetch all accounts, including those without any data that match your criteria.

In what scenarios should I convert multiple Custom Rules into a single Bionic Rule? 

• Rules which read from the same object can be combined together:

  • Different Custom Rules fetching from usage data for daily, weekly and monthly aggregations can be combined into a single Bionic rule

  • Cases when an intermediate step is needed to load data into an object which subsequently is used in another rule for transformation.

  • When there is one rule with “Load to MDA” action and another rule with some aggregation for business actions (eg. CTA, Set Score etc. )

    • Multiple task output actions can be leveraged where there is a slight change in the dataset tasks and actions need to be defined on a specific dataset task only

  • [S3 Ingest + Custom Rule ] can both be combined into a single Bionic Rule without the need for loading data into an MDA object.

  • Multiple Custom Rules and multiple actions are needed for Pivot use cases in Custom Rules. These can be simply combined in a single Bionic Rule

Will I encounter problems or limitations if I do not use Bionic Rules? 

The benefits of using Bionic Rules are many, so you do not want to delay learning how to configure them. However, your existing Custom Rules will continue to work for a while longer.

What is the overall timeline for retiring Custom Rules?