Property editor (beta) Update 1/23/26
Hi everyone,
I’m back with another update on the property editor beta. Over the past two weeks, we’ve been fixing bugs and making improvements to the new property editor based on your feedback, and we remain focused on removing friction to make your building experience smooth and intuitive.
Thank you again for your feedback. Below is a summary of the UX/UI improvements and bug fixes we’ve shipped, as well as those we’re actively working on.
Please note our next update will be in 3 weeks (week of February 9th), in order to make sure these updates start matching our product development sprint schedule.
What we’ve shipped since our last update
UX & UI improvements
-
We updated the background color of input fields across the property editor to have a better contrast between the fields and the property editor panel. We also updated the styling of dynamic and static parts of text expressions to make it easier to distinguish between the two.
-
Dynamic expressions now expand to fit their content, showing more of the expression by default instead of being limited to a few lines. You can see this in conditionals, element content, and event properties.
-
Long text fields like email bodies, HTML, and destination URLs will grow vertically as content is added and get their own line in the panel.
-
We added an accelerator to add all custom states of an element in the “Set an element’s state” action.
-
We removed leading icons from workflow parameters, return values, custom states, and fields to give more visible space for their content preview.
-
We updated icons and tooltip copy so it’s clear whether a conditional preview is currently on or off and what clicking will do.
-
We made all sections collapsable and decreased the click surface to expand/collapse sections to just be the section title. This should prevent erroneously collapsing sections when clicking out of fields.
-
Tooltips now appear after a short delay instead of instantly, making it easier to move around the editor without frequent interruptions.
-
We added bottom padding to the property editor panel so section tooltips are no longer cut off.
Bug fixes
-
Nested popovers in “Do a search for” expressions should no longer close unexpectedly.
-
Dropdowns using option sets as their datasource now correctly include the “All [Option Set]” option, matching the behavior of the original editor.
-
Sorting expressions now support dynamic expressions for whether the sorting should be in descending order.
-
We fixed an issue where fields were missing when using “each item: find and replace” operators on lists of text.
-
We fixed an issue where search constraints based on the unique id field would sometimes not show the equals operator as they did in the original property editor.
-
We fixed an incorrect warning copy shown for group data sources, so messages now correctly reference “this group’s content” instead of “this repeating group’s content”.
-
We fixed erroneous error states in reusable element properties when the default value of a property referenced a nested reusable element.
-
We fixed issues in the mobile action “Set property of current view” where property values were not reflected correctly in the property editor panel and switching between properties could leave fields uneditable.
-
We fixed the ability to delete conditionals on Input elements.
-
We fixed incorrect gap labels and behavior in conditionals for column layouts, including cases where row gap appeared instead of column gap or could not be removed.
-
We fixed layout and sizing issues in the color picker, including extra empty space and cases where the picker could extend off screen.
What we’re actively working on
UX / UI improvements
-
Clicking outside of popovers to close the open popover rather than leaving multiple popovers open at the same time and needing to manually close them all.
-
We’re reducing the number of clicks to navigate from the Design to the Workflow tab, preserving expanded state for which workflows are visible in the Design tab property editor, and enabling inline renaming for events and actions.
-
We’re adding the ability to switch from a color variable to its hex value for increased customization.
-
We’re improving the appearance of the “Only when” section on events and actions to highlight them more.
-
We’re updating labels, empty states, default expansion behavior, and click targets to make conditionals easier to build and edit.
-
We’re making several spacing, alignment, and border changes across the property editor for a more consistent layout.
Bug fixes
-
We are ensuring static number fields allow typing negative numbers starting with a minus sign directly.
-
We are fixing cases where color fields did not support dynamic values in conditionals like they previously had.
-
Fixed text selection in HTML conditionals
We are fixing the ability to highlight the content in HTML fields without moving their conditional row.
We’re also actively evaluating a few larger interaction changes based on user feedback. In particular, we’re exploring ways to reduce the number of popovers when working with dynamic expressions, including moving constraints and sorting inline for searches and making conditional expressions inline by default with an option to expand when needed. If we move forward with this direction, it would apply across other dynamic expression surfaces as well and have a meaningful impact on day-to-day editing.
Thank you again for the feedback and for your continued partnership. We’ll share another update the week of February 9th.
Thanks,
Mike
