Horizon Rules Bugs and Enhancements List (Last updated December 8th)

@rakesh I just wanted to give a shout out to you and your team for all of your work on the Horizon Rules migration. Our final item holding us back from moving fully from Bionic to Horizon Rules was resolved in the release over the weekend. We were able to test and migrate our final rule this week and now I believe we are fully off of Bionic Rules. Quite a project, but great work!

Something broke with the recent update.

The experience within transform with a lot of fields seems to have gone down hill. When I go into this tranform with a lot fo fields and try to scroll down it does not always want to scroll. It acts like there is nothing below it and remains on the fist X fields. 

Sometimes it fixes on its own. Other times I have to refresh go back in and scroll down.

Eventually after a bunch of scrolling up and down it realizes there are more fields and changes over.

But then if you let that scroll bar go away it reverts to thinking there are not more fields.

In a load to relationship action, 

can we remove the requirement of having Company GSID, Name, and Rel type like we do in bionic?

If I have the GSID of the rel and only doing an update why do I need these other fields?

Could we abolish that limit of a 100 show fields? That it’s not possible in individual fetch tasks is one thing, but once you’ve merged and transformed etc… it remains too limiting for snapshotting. I’m not sure why this was implemented as it’s not a thing in bionic. Also means I would have to migrate my bionic rules into two rules? I’m not psychologically prepared for such a mess. 

Not quite sure how this one has not made it on the list yet. 

But, there is some bug where a HRE page will take forever to load. The entire page becomes unresponsive and/or jsut goes white.

Worse yet this seems to affect all pages that are opened in that org making it impossible to go work on something else.

It is an intermittent issue. However, I and others come across it once a day minimum. I;ve gotten better at recognizing it as soon as it starts happening and thne close that page and reopen a new tab. But, that is not a good experience either.

Can we please get this added and fixed?

Can we get a Run Now Button on the execution page of the HRE? Seems pointless and needless clicking when we have to click back into edit mode just to click run now and then come back into execution logs.

This is a major problem and definitely inhibits my adoption (can’t speak for others). Every single time I try to open a newly migrated rule or create a brand new horizon rule, it crashes all my Gainsight tabs across all environments (Sandboxes or Production). The issue doesn’t quickly resolve itself either - i.e. a quick refresh of the affected tabs does not do the trick. It usually takes at least 10-15 minutes to resolve itself, if not longer, which is frankly a horrible experience. Also, if you’re in the middle of building something else when this crash strikes and hadn’t saved yet, you’re out of luck.

We’re running into this limitation too. Can this get fixed please @rakesh 

@spencer_engel 

It looks like it you change the action type to strictly Update the requirement goes away.

I’ve noticed two more things in recent days regarding Horizon rules: 

1. Horizon rules store significantly less execution history. Bionic rules hold roughly 40 recent execution history events, but Horizon only about half that. Why is this?
2. The rules migration error messaging is lacking. I had a migrated rule fail, and it turns out it was because it was an S3 rule that didn’t have the file in the bucket to reference. Makes sense why it failed, but I had to figure out on my own. The messaging said almost nothing.

Something that has been driving me crazy: Horizon rules apparently don’t have a unique URL? With Bionic rules, I used to be able to click into a rule and send the URL to my colleague or support and it would open up to that exact rule. With Horizon, when I try to do the same thing, it always just takes you to the Rules List. Is this something that can be addressed?

Wondering if anyone else has experienced this. 

I’ve noticed that when you migrate a Bionic rule with an S3 fetch the beginning of the file path gets removed. You can still preview the data for the file in the data set up step and test runs succeed. However, once you run the rule, you get the -1 error indicating it’s not able to find the file. Little bit of an annoying experience as we have a lot of S3 rules so we’ve had to manually go back just to add a file path that’s already in the Bionic rule being migrated.

Been a few months since it was requested.

But!!!!@!#!! You always appreciate when it finally comes through!!!!!

Cheers for saving me/all of us that extra click!!!

@rakesh I just bumped into a new feature parity request between bionic and horizon rules.  In Bionic Rules that load to Salesforce objects we could use a formula field as an identifier.  In Horizon Rules we cannot select a formula field as an identifier.  Please see ticket 310728 as an example.

Issue currently open with Gainsight Support: migrated rule that is mapping a string field to GSID cannot be updated