Product changes

image description

New feature - Request variables

For those of you who had troubles creating endpoints for an API that required specific data from the request, your aches and pains are a thing of the past. This release comes with a little pill called "the request variable" and it packs quite a punch!

The new endpoint request variable feature to read specific request values

Let's say you are building an incoming API endpoint and you need to know which IP address the request was sent from. Or if a certain application sends requests to your endpoint with specific headers and you need to read the "authorization" header for instance. Previously, there was no way of reading these values for endpoints. With the request variable however, you can. Each endpoint now has the option to add a name for the request variable. Simply give it a name and we will generate a custom model for you. This custom model can then be used in expressions or in your template with all the data you need.

Let's say you have named your request variable "request". Then "var:request.client_ip" yields the IP address, or "var:request.headers.user_agent" yields the browser the user used to visit your page. You can even use "var:request.body" in combination with the "xpath()" function to parse an XML request. This should be a nice addition to the tool bag for creating endpoints.

Read more

image description

New feature - App Switcher

Tired of navigating to to navigate to a sandbox or an entirely different app even? Do not fret. For the App Switcher is here!

The new App Switcher

This new feature, which can be found in the bottom left of the screen, allows you to quickly search for and navigate to applications.

To quickly switch between sandboxes of the current application, Mac users can use cmd + ; whereas windows users can use ctrl + ;

Navigating across organizations can be done using cmd + . on a Mac. When using Windows this can be done with ctrl + .

Read more

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

Experience Betty Blocks

this website uses cookies to improve your experience.