Product changes

image description

New feature - Custom model validations

Not long ago, we introduced custom models for webservices and for the the web endpoints. It is now possible to add validations to these custom models. Allowing you to build forms and flows that only save records when all fields have been filled in correctly.

Users will no longer be allowed to continue until they actually filled in a real email address or that terms-of-service checkbox has actually been checked by the user. 

And what's more is that you can now show the user which fields didn't get past validations. Validations for custom models can be based on actual model properties, although manual validations were also made available. 

Simply use the valid?() expression function in your condition events and proceed accordingly. You can then show the errors in your templates by using {{ var:my_record.errors }}

Read more

image description

Update - Improved platform-wide performance

Here at Betty Blocks HQ, we feel the need, the need for speed. And we felt that Betty Blocks really needed some love performance wise. This release brings some of that much needed love in threefold.


1) We managed to boost the performance of all backend activities. Using the builder or loading grids for instance are noticeably faster.

2) Using forms is now a lot faster, especially forms that use default values or have components with visibility conditions 

3) Web UI pages load a lot faster. In some cases even up to 3 times faster

Read more

image description

New feature - Count limited collections

How often do you need pagination for your Betty web pages? This will often lead to slow page loads. To help you build pages that load a lot quicker, we've introduced the count_full_collection() expression function.


Currently, if you want to paginate over a certain collection, you have to fetch the collection twice. Once with the limit and offset and once without in order to show a total count. With the count_full_collection() function, you can create a collection variable with offset and limit as you previously did (e.g. "products"). Now, however, you can create a second variable that counts all records for the given model and filter without the limit and offset, with count_full_collection(var:products). This should drastically improve the load times of pages where you paginate over large collections of data.

Read more

Experience Betty Blocks

this website uses cookies to improve your experience.