Over the last 4 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 44, 45, 46 and 47 of 2022.
Announcements
Pages
- Soon, we will offer a new way to define dependencies for components. This will enable you to more easily share and reuse components with dependencies (also via the Block Store), as we will automatically manage application bundles. Existing functionality (including uploaded bundles) will keep working as expected. Documentation will follow.
My Betty Blocks
- We will add a few improvements to the Block Store soon. This will enable you to better filter and sort. With the recent addition of new block types this is much needed, as it is now sometimes hard to easily find what you need.
Enhancements/features:
Pages
- Themes can now be saved and shared in the Block Store, meaning that you can install your stored Theme from the Store into every application you want. All details can be found in this blog post.
- Duplicating Pages that contain components with Next-gen Actions, also duplicates these Actions and its content. Steps and settings, such as Action permissions, are being copied. This only works for those Components that use Next-gen Actions.
- The new Forms can now be submitted when the Form is rendered on canvas. You can use this for example in Logic cases via SSO, as this does not require user interaction with the Form.
- A new Sub-view component is now available for creating relationships between pages in an easy way for your back office type pages.
- The Switch component is back in the new forms, just like in the previous form components.
Data
- Documentation around Mutations was updated on our wiki and Docs center.
Next-gen Actions
- You can now use a record as input variable in your action
- You can now send mails with attachments.
- Log compiler status is now visible in the new ide debug logging page (not available on Next Gen Cloud yet).
Templates
- Back Office Template has been updated with the following features:
- Search option can be set in the beforeCreate.
- Search bar added to the template.
- New Sub-view component available in the details view, you can now drag and drop a sub-view item in there for relationships.
- Actions can now be directly accessed from the wrapper, so no need to unlock the wrapper for that anymore.
- New Back Office V2 Overview and Record View templates are available. It’s the same back office as V1, but split into two different pages. With the same functionality as V1.
- All Page Templates are now NextGen compatible.
My Betty Blocks
Over the last couple of months we have added a lot of new capabilities to the Block Store. All details can be found in this blog post.
Fixes
Pages
- In the new Forms it is now possible to post a form without all Multi Autocomplete fields filled in. Relational data can be empty.
- The new Login Form Component broke when using the auto generated User Model.
- The File Upload Component in the context of an Update Form deleted the current file in some cases where this was not expected behavior.
- We’ve fixed that a Row Component ended up in a broken state, after deleting the Column via keyboard navigation.
- If you auto generated a new model in the Create new authentication profile flow the name of the relation inside the new model would be called Role instead of Roles, this is now adjusted.
Data
- Mutations with empty relation(s) are allowed.
- Playground returns better error message when creating many records using one query.
- Fixed CORS related issues when uploading files, where builders would receive a ‘network error: ajax error’ or other CORS related error.
- Roles can be added again, without the platform returning an error that ”the name already exists”.
Next-gen Actions
- As a builder I can't select all properties (when there are more than 50) in the value mapping settings.
- Using additional for collection or a record option will crash when the value is null.
- If a property name contains _<number> aren't camelized correctly.
My Betty Blocks
- Creating applications based on a template had certain issues (causing higher error rates, failed applications), we have taken measurements to stabilize the flow.
- On Next Gen creating apps based on a template was also broken for a short amount of time (for a different reason), this is also resolved.
- During a merge applications could get stuck when the name of the application was an exact amount of characters. This is now resolved.
- On zone NL1 it was not possible to delete builders/users from an application, this has been fixed.
- Searching in the Block Store always only returned results from the Public filter, now it properly adheres to the chosen filter.
That was all for now. Your feedback allows us to continuously improve the Product. So please, let us know what you think about it!
