We have updated our Component structure, to enable you to easily define its dependencies. This means you are now able to create (and use) Components with dependencies, without having to work with a manual component dependency bundle inside your application. Next to this you now can share and re-use these components via the Block Store, for other
We have added new capabilities to our Block Store, by adding 4 new Block types to be saved, shared and installed. This means pro-coders are now able to add more reusable functionality to the Betty Blocks platform in a very easy and quick way. Doing this enables them to easily reuse their work, but it also enables no-coders to build new use-cases.
Today we have migrated the existing application and native functions to a new icon structure. The icon field in the function.json is changed from a string value to an object.
What does this mean for you?
It means that when you publish your function, you will get a validation error and you need to change the icon field to the new structure.
The new
Enable a default authentication profile to create protected pages without the hassle of manual configuration. Rest assured, your pages and the data within are protected from the moment they’re created.
Authenticated pages
When creating a new page, builders can now make use of the default authentication profile to quickly and easily protect
We have released a first version of Role Based Access Control (RBAC) on Organization level in My Betty Blocks. This will soon have impact on 1 existing My Betty Blocks feature: the ability to merge changes (into a higher application level). In this post we will explain how you can now already prepare for this change, which will become active on
