August 5, 2025
13 days ago
This sprint, we focused on improvements to the user identity form, captures, and the admin experience of setup forms. Here are the changes released during the past two weeks.
New features and improvements
- User identity form:
- As soon as a user enters a unit where they haven't filled out all the required fields of the user identity form, they will be warned that required info is missing and offered to fill out the form.
- This enables administrators to rely on the user identity form data when creating recipes.
- When a user identity form field is used in a recipe, its value can now be captured.
- This enables users to store common alternate values.
- As soon as a user enters a unit where they haven't filled out all the required fields of the user identity form, they will be warned that required info is missing and offered to fill out the form.
- Captures:
- Captures are now private by default and can be published to become available to the other members of your organization.
- Users are reminded not to share sensitive information before publishing a capture.
- Any existing published captures remain published.
- Published captures can also be unpublished. This removes all existing subscriptions.
- Captures are now private by default and can be published to become available to the other members of your organization.
- Form setup:
- When adding multiple recipes to a recipe reference form field as an admin, the recipe picker will navigate to the previously chosen location.
- This should make it easier to add multiple recipe references from the same content source and folder.
- Combined form field types
TextField
andTextInputMultiple
intoTextField
.- Multiple lines are now a setting in the configuration of a
TextField
form field.
- Multiple lines are now a setting in the configuration of a
- When adding multiple recipes to a recipe reference form field as an admin, the recipe picker will navigate to the previously chosen location.
Bugfixes
- Fixed a bug where user identity form field settings were visible in the form editor, even though user identity form fields can only be edited in the user identity form setup.