Rules Horizon Feedback

I mean I missed the part where I could have acted and I appreciate you underlining it for me.

P.S. I’m already checking about opening up this particular feedback.

Thanks Product Council Admins for starting it off

@rakesh for reviewing

@bradley and @alizee for prompting to include the wider community - This Conversation is opened up for all the Rules-users to discuss.

Agree with all of the above:
Pros:

• Data designer UI to build the dataset is awesome!
• Because of this, the formula fields are "easier" to find (A-Z order at the general level, vs A-Z order by datatype in Rules Engine)
• And also, the "to string" fx that was only available in DD, now can be used in a rule

Cons:

• The Select an Object or Prepare Dataset action is weird/annoying. If you chose the former and then realize you need something else, you have to start from zero again.  So basically even using just one source I'll always choose the Prepare Dataset option just in case.
• The lack of capability to clone a branch
• The filter before the action is at the very least, inconvenient, any change in the filter will mean rebuilding the action

I just started building some simple rules so my insights are very limited, but I’ll circle back if I have any other feedback to share.

Overall, I like the new UI and being able to preview data sets with transforms/formulas without having to run test runs. 

Echoing the paint points that other mentioned: the amount of extra clicks, inability to clone branches, and the process for setting up criteria. Some of our bionic rules have ~20 actions with unique criteria. I’m not looking forward to manually creating a branch for each and every action 😅

Additional feedback on date filtering parity which I believe must have been shared elsewhere: date filtering in horizon rules was much less annoying than DD, combination of filters to achieve a Subtract or Add N Days from rule date is hellish. 

PROS: 

Overall, I really like the new interface! It’s much more user-friendly and I am a very visual person, so find the below items tremendously impactful.

• Data Design functionality is AMAZING! It’s a much cleaner experience and I love the consistent interface between the features
• Being able to visualize which dataset each action is running off of is also super helpful - especially when diagnosing failures. BIG fan of this!
• The execution logs are also very intuitive 

CONS:

I have already opened several support tickets for which I was told that the issue is a bug that Gainsight cannot fix. These bug fixes only fix net new datasets or net new rules, but not existing datasets/rules. The issues I’ve experienced so far:

• For extracts to S3, Display Name values are not appearing as column headers, regardless of being set to different values than Field Names
• One rule I built kept failing with the error: “Improper reference of taskId found in action.” This rule had a dataset that we deleted and then rebuilt the design within the same rule. The only solution was to delete the rule and build it again. GS did confirm a bug fix was shipped for this on March 10th and new rules should not experience this issue
• I keep experiencing strange behavior when using the “Duplicate String Value” option for dropdown fields. I’ll select that option, and save the rule. Then, I’ll delete the original dropdown field & change the display name of the string field to the field name of the dropdown field, and Save again. This appears to work, but then randomly the dropdown fields will reappear & the string fields will disappear. I have at least 3 rules where I’ve replicated this behavior successfully. 

Overall, I think the redesign is fantastic, and I’m looking forward to all of these strange bugs getting fixed so that my rules perform as expected & I don’t have to keep rebuilding them. 😅

Hey all,

I really like the Data Designer UI, it’s pretty handy to create rules.

I’m not that happy with the Action handling that was implemented, if you have multiple actions in different dataset tasks it’s not obvious which one is excecuted first. If you agree please vote here: 

Another small point I don’t understand is, why Picklist IDs are prioritized over Picklist Values. The ID’s of a picklist item is never used and not that easy to find. The Picklist Values as a direct string would be the way to go.

We’ll try using only Horizon Rules from now on. I hope that a few teething problems will be resolved before ending the BETA.

Best

Christian

Hi All,

Some feedback this end too - specifically around Horizon Rules and Relationships as well as some general UX thoughts.

From an admin perspective, I see the improvements and like the ability to preview as well as aligning the experience between Rules Engine and Data Designer, however, I have found a couple of pain points:

• Mandatory Lookups for Load to relationship etc. are slightly less easy to do - previously these were separated out into their own section nested under the action, however now it feels like it’s ‘map the field and hope’. I can imagine that for newer admins it’s confusing/stressful when trying troubleshoot rule failures, that wouldn’t fail on a test-run.
• I feel like I’m having to click through more menus/action points are nested deeper than previously - some of this will be bias/muscle memory but I find there are more steps required here - eg filtering the action separately from the action itself.

I will say, however that I find the ability to just fire a rule with from a general object vs. picking fields quite useful when I don’t need ultra-specific actions/joins and am just looking to change the defaults of some Booleans for example.

Best,

Leigh