Product changes

image description

Update - Validations on required input variables to actions

Variables could appear as input variables. This kind is used in actions and web UI pages to create dynamic content. Regarding actions, you can select whether an input variable must be required or not. Which basically means that the end-user who triggered the action has to insert a value for the variable. We updated this input field with validations. It validates if the required input field has any value or not.

Validations on required input variables in actions

Read more

image description

New feature - Customizable widths of back office pages

Back office pages (which are views) are used to load iFrames or to create manuals for example. A page can be added as a form’s subview. Previously you could only adjust the widths of data grids or forms as subviews. Now you can also adjust the width of a page as a subview. Insert the right pixel amount to preview pages to your wishes.

Adjustable panel widths of pages in the back office

How to adjust the panel width of a page? Create a page as a form’s subview. Click on it. Go to builder mode (or press ‘e’ on your keyboard) and click on the gear icon at the top left.  The edit page modal appears. Adjust the width amount, and press save.

Read more

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

Experience Betty Blocks