Released:
Schema fields can now be of type relationship, referencing entities from a target schema with one or many cardinality.
Relationship fields support:
list (default) or table for many-cardinality relationshipsExisting schema relationships can be converted to inline relationship fields. This is currently in Beta testing - reach out if you want to transfer some of your historical Relationships into inline relationship fields.
Date fields support two new configuration options:
A User admin settings page, User Settings > Timezone & Locale, provides system-wide defaults.
A new batch entity context type collects descendant entity contexts for coordinated batch save operations and unified dirty-state tracking. This enables multi-entity forms where all changes are saved together.
Buttons now support a CRUD action kind with four operations:
create - create a new entity from the bound context.update - save changes to an existing entity.delete - Remove the bound entity.save - save all dirty entity contexts (works with batch contexts).On-success behaviour is configurable: reset the form, refetch data, or navigate to another experience.
This means that you no longer need to create a Flow to save Entities!
Entity contexts support field overrides with two modes:
default - seeds the value on new entities; remains user-editableenforce - always overrides the value at save time; renders bound inputs as read-onlyOverride values are resolved via data expressions, enabling dynamic defaults from URL parameters, parent contexts, or other datum references.
The data expression node now supports a js mode backed by QuickJS, alongside the existing expression mode. JavaScript mode enables:
Instant, ZonedDateTime, PlainDate, PlainTime, PlainDateTime) with arithmetic and comparison operationsSQL credentials and query workflows received several improvements:
The object:query The flow node now enforces a maximum result limit of 1000 records per execution. The entity listing API validates limit at the input boundary.
AI data extraction mapping now includes standard fields (e.g., createdAt, updatedAt) alongside schema-defined fields, enabling richer extraction mapping configurations.
Fixed text template variable formatting options not being applied during flow execution. Format directives in content serialisation are now correctly resolved.
The List Filter node's "Distinct By Field" option now supports selecting multiple fields for distinctness checks.
Space dashboard search results are now sorted by relevance rather than creation order.
managedRelationships injection during entity updates - relationships are now correctly synced on update, not just create.Instant and ZonedDateTime objects are correctly serialised in Data Expression.Instant and ZonedDateTime arithmetic and comparison operations in Data Expression.Related Releases
Related Releases