Product changes

image description

New feature - Authentication profiles

Applications are sometimes faced with a complicated login schema to authenticate different user profiles. For example, one profile authenticates with Microsoft ADFS, another with the internal Betty Blocks authentication or username & password. You want to manage and simply apply these different profiles in your application. Therefore we made this new feature called authentication profiles. Here is what we have done:

 
A quick introduction to the new authentication profiles

A Betty Blocks application can have multiple authentication profiles. These profiles are managed in the new view under Settings. Every application has the Internal Betty Blocks profile. Which means that you can authenticate web pages with Betty Blocks accounts.

Your webuser definition in My Betty Blocks (Settings > Login) is migrated to the new authentication profiles. This has only been done, if a webuser definition was created. The name of this profile is Username/Password by default. We migrated the password's ShaBit length setting to the password property itself, because that setting belongs to that property type. Check out this learn article for more information about what authentication profiles are.

How do I apply authentication profiles? You can use a profile to authenticate web pages with. If your page requires authentication, you have to select which profile users (who enters your page) have to authenticate themselves with. For example your customer portal requires authentication with a username and password profile. In this profile, you have selected a redirect page in case a user isn't logged or the user's session is expired. Users are probably redirected to a login screen. The action which processes the login flow contains a login action event. We have slightly changed this action event too. It now requires a profile to authenticate and to login or logout. We also changed the name of the event into 'authenticate and login user' to be more clear what it does. Please read this learn article for more information about how to apply authentication profiles.

Read more

image description

New feature - Filtered input variables by var:record

We have built a new feature for input variables at actions in the back office: filtered input variables by var:record. You can now use var:record to filter input variables with the kind 'object'. Why? Because filtered input variables by var:record show even more relevant data in the dropdown. We made a short tutorial to show you how it works:

 
Filtered input variables by var:record in actions

Read more

image description

New feature - Assigns in the import action event

Over the past weeks, we introduced all kinds of new features in the import event. You can process imported records by a callback action to use them in subsequent events for example. However, we wanted to go even one step further. Because what if you want to assign values to the whole import file before every record has been validated? Therefore, you can now use the assigns in the import event. You can use this to relate all import records to a file, client, user, etc. Here is how it works:

 
Assigning values to all records in the import event

Read more

Experience Betty Blocks