Let’s compile all the requests for how Rules can improve on the new record layout in one place.
I figure it’s better here as a feature request than to overrun the comments on the initial announcement post on Rules from back in July of 2025 🆕 Introducing: Rules
I came looking whether a specific feature request already existed, but I couldn’t find the one I needed.
I know however that I’m guilty of forgetting something that’s already been shared in this community, even when I was the one to request it originally.
Then this recent post from @dirk_s made me start thinking about other ideas that have come up in past threads, but maybe slipped away without officially being logged.
As I’ve been using more apps with the new record layout recently, I’ve started thinking of many more ways I wish I could use Rules in the new record, like Dirk’s hidden if NOT empty.
I figured I’d post a few here in this one thread, and invite others to add their ideas so that our friends at Tape don’t have to go digging for feedback when they are ready to add features to the rules.
For starters - Hidden If Empty with Rules.
@Leo confirmed this one is coming soon: New record experience: now in public beta 🎉 - #25 by Leo
Next up: Hidden if NOT Empty.
As described by @dirk_s
“hidden if not empty” would be as useful as “hidden if empty”.
In processes there are certain fields, which only need to be set once and never be changed again. You don’t even want to see it anymore. If needed at all, I could still show the hidden field again, same way I show “hidden if empty” fields manually.
Again, Leo did confirm it’s on the radar: New record experience: now in public beta 🎉 - #27 by Leo
Hide/Display based on mathematical validation.
Example: We have some number fields that split out what % of a sale gets attributed to up to three different users. We would love a big red warning label to appear on the page if the sum of number field 1 + number field 2 + number field 3 does not equal 100%
Because rules are available on things like text blocks, title fields, and even images, this would be fairly simple to utilize, but we’d like to build the rule based on our math rather than requiring a separate calculation field to do math, and then a rule based on that field.
Hide/Display based on conditions other than select type fields.
Ap present, there is a known limitation that rule conditions are
based on select fields (single select, multi-select, and status)
Several times we’ve had an idea for a rule and wanted to set it based on things like single line text or other value settings, but it’s not yet possible
I should add, the Tape team did already share this ‘vision’ of potential applications for rules that might be released in the future: