Skip to main content

I was doing some comparison between a Bionic Rule and a Migrated Horizon version of it and thought I had encountered a problem:

 

Bionic Rule execution history record count:

 

Horizon Rule execution count:

I expected the same result, and on initial look thought there was something wrong with the setup so I went to download the HR logs to check, and discovered that on mouseover you get the actual numbers:

 

It may seem like a small thing, but not having the actual counts without mouseover really cuts into the great benefit of having the whole execution flow “at a glance” (well, unless you have more than three actions off a task).

 

It would be very helpful to have the actual record counts, not a rounded number, be visible in the execution history.

Absolutely agree!
There is more than enough space to show the full number, having to go dataset by dataset hovering over them to see the actual count is inefficient when we could get the info we need at a glance.

Oh yes….100% agree.

I’d benefit from understanding why behind the decision to use rounding, because perhaps there’s a compelling reason I’m overlooking.

Rounding makes sense in use cases where precision is less critical. However, running and troubleshooting rules is typically a very precise activity. I’ve had many occasions when I’m stepping through logs and noting “OK, I got 13,916 rows here, but in the next step I ended up with 13,901, so something happened to 15 rows that needs more research.”

 

I’m on board with this. Even a minor difference of a few records can be very meaningful depending on the rule, and I like to browse these over time to get a feel for the expansion in various objects. Rounding is too broad here and we don’t need it.

No Status→Acknowledged
Terms & ConditionsCookie settings