Over the last 2 weeks, we have been working on improvements to the platform. In this blog post, you can see a simple list of what has been changed, updated, and/or what bugs have been fixed. Read more about the release notes of weeks 08 and 09 of 2022.
Enhancements
Platform
- We have improved the stability and performance of our NL3 cluster by upgrading the storage on our database servers and optimizing storing the options on components You can notice these improvements in:
- My Betty Blocks, managing your applications and their changes
- Building your application within the IDE
- Compiling your application to the runtime environment
Page Builder
- We have increased the performance of compiling pages by adding caching, when the caching is available the compile will take less than a second instead of more than a minute.
Data
- The new Data API Mutations now supports uniqueness validation.
- The new Data API Mutations now supports multi-single updates. You can do a mass update in a GQL mutation. Each object (unique identified) can be mutated individually.
- The new Data API Mutations now support an update mutation with hasMany relations so you can update many records with filter that can use relational properties.
Templates
- The Dynamic Questionnaire template has been released. This template allows you to create dynamic questionnaires, which you are able to send over to participants, who can then fill in the questionnaire. Questionnaires have 5 types of questions available, which you can dynamically show and hide based on your input.
- The Case Management template has been released. This template allows you to set up a case management application quickly and easily. It has some basic steps already ready for you to start working with it. The set-up should allow you to quickly add new fields and pages to extend your application to your needs.
My Betty Blocks
- When you select the role for an organization user (in the user overview and soon also while inviting a new user to the platform) this is now done via a dropdown list, instead of a radio button.
- When your application is stored in a trial organization, you can’t promote your application to production. With this, we enable our customers to govern the live applications of their company in just one place: the official organization of their business.
Fixes
Page Builder
- You will no longer get errors while loading pages due to template applications that did not set a component scope resulting in fetching too much data.
- The helper text of autocomplete components is no longer displayed twice in certain cases, if you experience this in existing components re-add them on the canvas.
- Searching for a non-existing value in the single value autocomplete no longer results in an error.
Data model
- Update mutation is not returning a wrong id anymore when the record is not updated
- No more error when two properties have the same name in one data source
My Betty Blocks
- Previously, specific symbols were not recognized when used in the password. Now the user can use all symbols.
- Removing a search (by pressing the X button) didn’t work, this is now resolved.
Announcements
Actions
- The new Actions environment will be launched over the coming weeks. This new environment will be made the primary source as much as possible for newly created actions. Initially, this will mean the Actions Overview and Quick Menu show Actions of this new type by default. Navigation to existing Actions, in order to view or edit them, is of course still possible. Over time, more functionality besides the Action Overview will use the new Action types by default. We will inform you on time when those changes will take place.
My Betty Blocks
- On the 15th of March, the Private Data Mode (PDM) will be activated for all applications with the status Development in order to secure the runtime from public use. Take into account that the email settings need to be changed to SMTP or Mandrill when promoting your application to production.
- The permission to merge applications will soon no longer be automatically tied to the builder role (on app level), but to the new roles & permissions structure on organization level. This might require you to change some things to make sure the right people can merge apps. We will inform you up front, so that you have time to adjust the new organization roles & permissions before the merge changes button will adhere to the new permission in the interface.
That was all for now. Your feedback allows us to continuously improve the Product. So please, let us know what you think about it!