How do you set the order/ranking of Data Rules in Application Studio?

Kinetic ERP
,
1

Is there no way in Application Studio to tell it which Data Rule takes precedence over another on the same data view, like you can in the Classic dashboard by putting the most important above the rest?

I’m trying to recreate two row rules that I had on a classic dashboard, where the first one on the list looked at a percent complete column and set the style for the whole row to “OK” for anything greater than 99.999999. The second rule sets the whole row status to “Warning” when the percent complete column is greater than 90. In Classic, this perfectly colored the rows with percent complete between 90 and less than 100 in yellow and anything 100 or above as green.

Recreating this in Application Studio (version 2023.1.5) is not as obvious—assuming it’s possible. I’ve tried creating them in the order I want them to go, by both creating the most important first and then in another attempt by creating it last. That didn’t make any difference. I tried creating each of them in different layers, starting with the most important one in a layer and then the next one in the next layer (this layer did show both rules, whereas my first layer doesn’t), then setting the customization order to be the same sequence. That didn’t change anything either.

2

How is it not working? Are they always yellow, green, another color? You have described what you want to happen, but have not told us what is currently happening with your attempts.

3

As it’s working now, it’s highlighting everything above 90 as yellow, including anything that’s 100 or greater, when those should be green and are in the Classic version.

I know that I could add a second condition to the “yellow” rule to also be less than 100 (right?) so that it’s only looking at the >=90 to <100 range, but I’d really like to know if there’s a way to stack–for lack of a better word–rules like you can do in Classic.

4

I know what you are talking about with the “stacking”. I have not come across needing to do this in Kinetic UI yet, so I can’t give you an answer as to whether it can be done. I would just add the second condition like you say.

I came across something similar in BPM conditions needing to be exact when they did not have to be in 10. This sounds like something similar that probably changed in the Kinetic UI.