1. New features and user-requested adjustments

Improvements

Group field subfields can now be configured as read-only

Until now, it was not possible to configure subfields of a group field as read-only.

With this improvement, each subfield can be configured independently. For example, it is possible to have part of the group editable by the user and part filled by the system and locked for viewing, without needing to duplicate fields outside the group structure.

Want to learn how to configure group-type fields? See the documentation.

Field events now automatically open repeater rows

When a field event was configured to copy the payload from one repeater to another, the system was unable to create ("open") the destination rows at the time of the event. The result only appeared after saving and reopening the item, giving the impression that the automation had not worked.

Now, when triggering an event that copies payloads between repeaters, destination rows are created and opened automatically, and the filling happens immediately and visibly.

Want to learn how to configure field events? See the documentation.

Relationship field events now correctly propagate links

When a field event was configured to copy the payload from a relationship field to another, the information was not loaded correctly.

The fix ensures that the relationship payload is reliably copied between fields, correctly using the references configured in the event editor.

Want to learn how to configure field events? See the documentation.

Repeater with fixed or dynamic number of rows

In some scenarios, it makes sense for a repeater to open with a predefined number of rows, either because the quantity is always the same or because it depends on another field in the form. Before this improvement, building this type of configuration required field duplication and complex conditionals.

With this delivery, the repeater now supports a predefined number of rows, both in list and table mode, with two forms of quantity control:

• Fixed: the configurator defines how many rows the repeater should always present — and the user cannot manually add or remove them. A use case example: in an HR evaluation, the repeater can be configured to open exactly 3 rows, one for each role the evaluator must indicate: manager, supervisor, and peer.
• Dynamic: the number of rows follows the value of a controller field, which can be a number-type field or a single-select with numeric values in the options. For example: in inventory control, if the user enters "4" in the "how many new items arrived?" field, the repeater automatically opens 4 rows ready for filling.

Want to learn how to configure repeater-type fields? See the documentation.

Fix in the external task email template

In external tasks generated by Spaceflow with email sending configured as "no layout," the email arrived without the task access button, and the alternative link appeared as plain, non-clickable text, forcing the user to manually copy and paste the address.

The fix ensures that, even without a layout, the recipient receives a functional path to access the task, whether through the button or a clickable link.

Want to learn more about Spaceflow? See the documentation.

Bug fixes

Repeater subfield order in form-type folders

When a form-type folder displayed data from a repeater, there was a problem: the subfield order shown in the folder was determined by the order in which they were created, not by the configured order.

In practice, if the configurator created the "age" subfield before "first name" and "last name," but then reordered them in the configuration to first name → last name → age, the folder continued displaying age → first name → last name.

The fix ensures that the order displayed in the folder always respects the configuration defined by the configurator.

Option to hide subfields in repeaters

Even with the "hide in repeater" option enabled, hidden subfields remained visible. The fix restores the expected behavior: fields marked to hide do not appear in the repeater interface.

Repeater subfields in reports

Reports did not correctly handle repeater subfields, causing this information to appear blank in the export. To solve the problem, it was necessary to ask a developer to enable extraction via database.

The fix ensures that repeater support in report generation works correctly, allowing extraction of nested data selected in the builder.

Error in report generation

In dedicated environments — workspaces with their own URL — report extraction was failing, preventing downloads. The fix eliminates the error and restores normal report generation.

Sorting by custom fields in the items screen

In the upper right corner of the items screens, there is a sorting filter. It can use native fields and custom fields (created by the user) as a basis for sorting. When trying to sort items based on user-created fields, the system returned an error, while filters for default fields worked normally.

The fix restores the filter for custom fields, ensuring its proper operation.

Error when completing a task

Specific users were encountering an error when trying to complete a task, which blocked the flow's progress. The cause was related to temporary absence feature data linked to members who had been removed from the workspace.

The problem occurred in a specific scenario: when the member configured as absent was later deleted from the workspace, the absence data associated with them had no valid reference. When trying to complete a task in this situation, the system found this invalid reference and did not allow the task to be completed.

The fix makes the task completion process resilient to this scenario, ensuring that absence records linked to removed members no longer block flow progress.

Tip: when a member leaves the organization and already has tasks, items, or other data linked to them, consider deactivating them instead of deleting them. When deactivated, they lose access to the workspace as expected, but all references to them are preserved, maintaining traceability and record integrity for audit purposes.

2. General product evolutions and fixes

Improvements

DocuSign: pre-configuration of signature placement

The DocuSign integration now includes a new pre-configuration flow: before the document is sent to participants, a workspace member takes the role of configurator and defines exactly how the document should reach each recipient.

This configuration is mandatory for the integration to work. The configurator receives an email with an invitation to access the platform and, within the integration task, make the necessary definitions — such as positioning each participant's signature fields, indicating initial locations, inserting stamps, and applying other actions available in the tool.

Once configured, the document is sent to signers with all fields correctly positioned, eliminating errors and rework.

Want to learn how to configure signature placement? See the documentation.

Spaceflow: CRUD node now supports more field types

The CRUD node previously accepted mainly Text, Number, and Date fields. This limitation prevented more complete automations in workspaces with more elaborate configurations.

Starting with this release, the CRUD node now works correctly with selection and relationship field types.

Want to learn more about the CRUD node? See the documentation.

Spaceflow: CRUD node now supports item reading

The CRUD node already allowed creating, updating, and deleting items in the workspace. With this delivery, the Read One action, which was available in the interface but disabled, now works.

With Read One, it is possible to search for a specific item within a category based on a filter — and the first result found is available as the node's output, which can be used in subsequent flow nodes such as emails, conditionals, and documents. Filters accept flow variables in the {{ }} format, allowing dynamic queries — for example, searching for an item where the ID number equals the value received in the flow trigger. If no item is found, the node returns an empty output without generating an error.

Want to learn more about the item reading feature in the CRUD node? See the documentation.

It is now possible to create custom views directly via the New view button, available at the top of items and tasks screens.

With it, the configurator can create screens with specific display criteria, combining filters by custom fields, conditionals, groups, and roles — crossing these criteria to build exactly the view each user profile needs. The created views work in both table and kanban mode.

Spaceflow: "link item to the task" field now accepts reference variables

The link item to the task field — present in all Spaceflow nodes that generate tasks — is responsible for linking the item to the created task, allowing the user to access the item and see, in the Spaceflow folder, the task data related to it.

Until now, this field did not accept reference variables via drag-and-drop method (dragging a variable from the input tab to it).

With this improvement, the field now accepts reference variables. This means it is possible to automatically link the task to the correct item by dragging, without needing to search for the correct variable in the field list.

Spaceflow: "completed by" field is now recorded in external executions

In external task executions of Spaceflow generated by manual CRUD nodes, the completed by field — which records, in the Spaceflow executions screen, the email of the user who completed the task — returned empty, making it impossible to identify who had completed the execution.

The adjustment ensures that the field is correctly filled in external contexts, and it can be viewed by clicking on the output details of a CRUD node that generated an external task, in the Spaceflow executions screen.

Member management: invitation improvements

The member management screen received three improvements related to invitation control:

• New "Invitation Status" column: the screen now displays each member's invitation status in a dedicated column, with distinct visual indication for pending and expired invitations. Previously, there was no way to identify this status directly in the listing.
• Expiration date renewal on resend: when resending an invitation — whether pending or expired — the expiration date is automatically renewed. Previously, trying to resend an expired invitation returned an error.
• Bulk resend: it is now possible to select multiple members and resend invitations all at once, without needing to do it one by one.

Documentation: new experience on the versions page

The Versions page in the documentation has been redesigned. Previously, releases were recorded with shorter, more direct texts. Now, each published version has a complete blog post with a detailed description of everything delivered in that deploy — like what you are reading now.

The Versions page continues to function as an index, listing all releases with a summary and a direct link to the corresponding post, maintaining the complete history of all published versions.

Documentation: menu reorganization and global search

The documentation received two structural improvements that make navigation and content discovery easier:

• Menu reorganization: the page and menu structure was reorganized to reflect ENSPACE's internal navigation. Previously, the organization did not follow a defined pattern, making it difficult to find the right content.
• Global search: there is now a global search field in the documentation menu. The search is not limited to menu names — it also scans the internal content of pages, making it much faster to find any information.

Homepage documentation link fixed

The documentation button on the ENSPACE homepage pointed to the internal testing environment (stage) instead of the official documentation. The fix adjusts the link to the correct destination, preventing users from consuming outdated information.

Bug fixes

Calendar and holiday configuration

In all workspaces, the holiday customization option had disappeared and the calendar view stopped working as expected.

The fix restores both the calendar view and the ability to configure holidays and business days.

Quick tasks Kanban: assigned responsible

In the sidebar that opens from the "view" action on Quick Tasks Kanban items, the assigned responsible appeared incorrectly in two scenarios: when it was a member selected in a fixed way in Spaceflow, it displayed an internal ID instead of the email; when it came from a Spaceflow variable, it was blank.

The fix standardizes the display to show the responsible's email in both cases.

Translation of help text in field types

The help text displayed in field type configuration was untranslated in some cases. The fix standardizes the translations, improving the experience for those configuring the workspace.

Translation of unique value validation in repeater

The uniqueness validation message displayed during repeater filling had incorrect text. The fix adjusts the text, making the message clearer for the user.

Workspace icon editing

The action to edit the workspace icon had no effect: no changes were saved. The fix restores the expected behavior.

Repeater in table mode: alignment fixed

In the repeater's table mode, some field types appeared misaligned, impairing readability and filling. The fix sets the correct alignment.

Email resend is working again

The button for the email resend action on the emails screen did not execute anything. The fix restores the resend trigger.

Relationship fields in tables: width limit applied

The content of relationship fields was exceeding the column width and overlapping other columns in tables and queries. The fix applies a width limit, maintaining the grid's visual integrity and improving readability.

Kanban scroll: position preserved on update

In long Kanban columns, the scroll had unstable behavior: when trying to scroll a lane down, the column resisted and moved slightly back up on its own. The same happened in reverse when trying to scroll up. The result was a locked-up navigation that made it difficult to access cards in the middle or end of longer columns.

The fix stabilizes the scroll behavior, allowing navigation through Kanban lanes without interference.