The Ides of March are behind us, and while others may still beware, our team carries on undeterred with this week’s update. Let us march on:
Our engineers have:
Added Display Rules in Custom Components:
We’ve added advanced display rules to Universal Components, bringing similar functionality previously available in Tables and Lists.
This update improves flexibility by allowing you to define rules at the component level, rather than only at the field level. Within each rule, you can choose which fields the actions apply to, such as changing colors, or apply the rule across all fields in the component.
This makes it easier to manage styling and logic in a more centralized and scalable way.
We’ve also added the ability to create rules based on logged in user conditions. For example, if you have a Connection field to the Users table, you can define rules based on whether that user is logged in, not logged in, or belongs to specific roles.
This is not intended to replace security at the layout, page, or row level, but rather to provide front end visual control based on user context.
Here’s an example of a single display rule applying different actions across multiple fields 
:
Enterprise Search Enhancements:
Search by Connected Fields
The Enterprise Search Component now allows you to search using connected fields. For example, if you have a Jobs table, you can filter jobs based on fields from connected tables like Users.
This means you can now dynamically filter results such as showing only jobs where the connected user’s email contains “example.com”.
While this was previously possible through static table filters, it is now available dynamically within Enterprise Search, making advanced filtering much more flexible for end users.
Validation Rule Updates:
Match All and Match Any
You can now define validation rules using Match All or Match Any logic, giving you more control over how multiple conditions are evaluated.
AI Prompt Update:
Temporary Fields
Added support for temporary fields in AI Prompts, allowing you to handle intermediate values and responses more flexibly within your AI workflows.
The curtain falls on this one, Tadabasers. Happy building and see you next week! 