Are Bionic Rules getting retired in July?

Please. No. 

Current status on this from internal discussions i’ve been on is that no, unmigrated Bionic Rules will not be auto-migrated at end of July on Release weekend.

The current plan:

• After Release Weekend (last weekend of July for US1 NXT - a week earlier for EMEA), you will only be able to create net-new Horizon rules -- when creating a new rule, Bionic Rules won’t be an option as the type of rule to create.
• Existing Bionic rules will continue to run as-is and be editable -- the target date for deprecating Bionic and auto-migrating any active Bionic rules to Horizon is slated for early 2024.

The Product Team will chime in here with more details soon, but wanted to make sure you knew that you will not wake up on August 1 and find all your Bionic Rules have been auto-migrated to Horizon!

@sdrostgainsightcom I think it is semantics on this one.  Ultimately, admins will no longer be able to create new bionic rules after the July release.  Just because the bionic rules won’t be migrated in August doesn’t mean that this doesn’t create a hardship for most admins.  We will be forced to use Horizon rules for anything new after only 4 months of Horizon being GA.  No warm fuzzies here.

I totally understand @Angie.Walsh  -- and I assumed that my answer wouldn’t 100% put Admins at ease, but I at least wanted to be sure everyone knew that it was not a case of deprecating existing setups on this first planned move to Horizon.

I will let Product take over from here next week in the discussion, but I do know that closing gaps and tracking issues are top priority for that team thru July as well -- and along with opening a ticket, definitely want to see Admins posting issues they are seeing on this channel as well here.

Thank you for focusing the discussion - I’ll keep an eye on responses next week!

Should we move this discussion then to the ‘Idea’ section and change it the title to “Please wait longer before cancelling Bionic Rules”?

Thanks @sdrostgainsightcom .  I know this isn’t you or your decision. I appreciate the insight and the fact that some people from Gainsight are beginning to let others know of this change.  

This is madness.

Gainsight has had a history of not-so-successful attempts to forcibly move customers to GA features before (Bionic Rules, Horizon Analytics, Horizon C360 to name a few).  

Now you're talking about only giving customers 6 weeks notice (by means of word-of-mouth, apparently) to switch away from using Bionic Rules - the most critical Gainsight feature - to Horizon Rules only 4-months after it GA'd and after two months of platform instability?

Any experienced platform manager knows you don’t fully adopt 1.0 versions of a feature until after a couple of release cycles to allow it time to have the major kinks worked out. 

Forcing our hand so soon after GA is not the way to set your customers up for success.

until after at least couple of release cycles

Thanks for creating this thread. I agree 100% with the sentiment here. With some of the issues I have encountered, I believe it would be a big mistake to remove the ability to create Bionic rules this quickly. 

To add on, here are just a handful of the issues I’ve seen come up in the slack work group. Are all of these things fixed or identified as bugs? Also building a workaround is not the answer as that can get complicated for some admins.

• Issue of not being able to filter for ID's. https://community.gainsight.com/ideas/horizon-rules-and-ids-45763
• Page Timeouts
• A Mechanism to migrate rules and not have to manually go into each one and set schedules or rebuild rule chains
• Have the above bullet tested but handful of clients
• Issue of seeing backend naming conventons when adding a task onto another, seems intermittent. Screenshot 1
• Horizon items are not showing up in dependencies in multiple places
• SFDC to MDA picklist comparisons/working with them. rules treating MDA options as gsids and SFD as actual string.
• issues with the Horizon rules? It just spins, and nothing happens when I try to update the actions section, https://globalgainsightadmins.slack.com/archives/C01H3GB97PX/p1685725952885289
• Horizon Rules straight up refusing to load Action Criteria page on one of my existing rules. Not migrated, HA native, https://globalgainsightadmins.slack.com/archives/C01H3GB97PX/p1685453064563019
• Horizon Rules Bug: For some rules with Set Score Action, the Scorecard selection shows duplicate Scorecards even though you only have 1 of them created. This was found after the rule was created and a test run completed, but seems to only be for one of my Scorecards not all. https://globalgainsightadmins.slack.com/archives/C01KD2A5NSZ/p1685108038834229
• Since it is related, I will just add to this thread that we did have a Salesforce field API name change at the source. After the name was changed, I could not open the filter on any of my Horizon rules where the field was referenced in the Data Design. Support told me the only thing I could do was delete the node and re-add (which of course it was the first node, so I basically had to re-do any rule that had this Account field filter). They said it was a bug in Horizon rules. The issue did not happen in our Bionic rules. https://globalgainsightadmins.slack.com/archives/C01HCPYQKS8/p1685540030727999?thread_ts=1685535490.591419&cid=C01HCPYQKS8