Removed case sensitivity for SSO signup and sign in
We have updated the case-sensitive validation when creating an account. If a user creates an account, the case of the email address isn't taken into account. So, for example, FirstnameLastname@mail.com is now considered the same account as firstnamelastname@mail.com. For more on single sign-on, see our knowledge base article, About single sign-on.
Delete all data shows a different message when a model has no data
If you select Delete all data on the schema page for a model with no instances, we've added a different message. "This model has 0 records. There's no data to delete." See our knowledge base article, Delete all of a model's data.
Add subresource integrity to scripts
We've added Sub Resource Integrity Attribute to scripts to prevent an attacker who has gained access to the server from injecting malicious content.
Restrict the "Has children icon" list to only show supported icons on the hierarchical block
Previously when you added a hierarchical block to a page, you could see a complete list of icons in the Has children icon list. However, not all the icons were supported. Therefore, we have restricted the list to only the supported icons. See our knowledge base article, Add a hierarchical block to your page.
Clearer page titles for content blocks
We've updated the page and dialog box headings when editing content blocks. Instead of the hard-coded text "Content" for all content blocks' and search settings' page titles, we have updated this to be the text "Settings: {block title}" instead. For example: "Settings: My custom form."
Always show the version number in the burger bar
We've added your Applaud platform version number in the burger bar, regardless of screen size.
User and role conditions for form interactions
We've enhanced form interactions so you can add certain user and role-based conditions to a form so you can show or hide relevant fields and update fields accordingly.
When adding a form interaction and selecting your conditions, you can now select the email property and all custom user properties from the User model.
Email can be helpful when you have employees with multiple email domains representing different brands, for example, firstname.lastname@company.com and firstname.lastname@companybrand2.com. Here you can use "contains any of company.com."
You can do this for any additional properties you add to the User model. For example, you can use the User - role "Is known" or "is unknown" to detect whether the current user is anonymous or not. You can choose one or more roles from the Value list.
When you select the "Owner user" field, you can select user properties on the Value side, for example, userId and User - Id. See our knowledge base article, About form interactions.
Option to allow multiple dates to be selected in a date range property
We've added a new option when creating a date range property type:
- Allow individual dates to be selected
Instead of a sequential range, the new option shows a single field and lets users select multiple random dates on a form. See our knowledge base articles, Property dialog, and Add a property to your model's schema.
We have also changed the edit field options for a normal date range. You can now keep separate From and To fields, or you can select to have a single field as the new date range option. Again, this is to aid backward compatibility. See our knowledge base articles, Edit field - date range, and Edit field.
This shows two separate fields as previously and is selected by default.
Alternatively, you can select the single field option:
This shows a single field:
Show release name in the version number
If the release has a name, this is now shown after the release number in brackets:
New option to sort task list by Name
Previously you were only able to sort the task list by date. We have added the option to now sort the list alphabetically by name. See our knowledge base article, About tasks.
Updated date picker
We've updated the date picker with the Veutify material design.
It can feedback to the user on which dates are unavailable.
The date picker also changes to fit with your brand:
Set row form interaction for multi-select foreign keys
We've added a new Set Rows action to form interactions to copy a field value from a form field to a linked model form field.
The new Set Rows action copies the value set in the field to a field in the linked model field. For example, when a user selects multiple dates in a date range property, "Time off dates" in the primary model, a new row is added for each "Daily date" in the "Daily breakdown" linked model, and the date value is copied to the "Daily date" field.
Aggregate rows form interaction
We've added some more actions to the form interactions so you can count rows, calculate totals and averages, and show the minimum and maximum values.
Count Rows |
Counts the rows of the linked model and displays the value in the selected target field. Typically, you would use this in conjunction with the Set Rows action. ![]() |
Sum Column |
Calculates the total value from the values of a selected field and displays the total value in your selected target field. Typically, you would use this in conjunction with the Set Rows action. ![]() |
Average of Column | Calculates the average value from the values of a selected field and displays the total value in your selected target field. Typically, you would use this in conjunction with the Set Rows action. |
Min of Column | Finds the lowest value from the values of a selected field and displays the minimum value in your selected target field. Typically, you would use this in conjunction with the Set Rows action. |
Max of Column | Finds the highest value from the values of a selected field and displays the maximum value in your selected target field. Typically, you would use this in conjunction with the Set Rows action. |
Improved performance for forms
We've improved the way forms update, so the response is quicker when configuring a form block. See our knowledge base article, Add a Form block.
Icon list when configuring hierarchy content block
We've restricted the icon list to only show supported icons on the hierarchical block and alphabetized the list. See our knowledge base article, Add a hierarchical block to your page.
Support for criteria in date field form interactions
We've added technical user interface support for date fields in form interactions. See our previous notes in our knowledge base article, Support for criteria in date field form interactions.
Comments
0 comments
Please sign in to leave a comment.