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
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
New feature - Advanced model property validations
Not long ago, we introduced the feature ‘validate by expression’. This feature made it possible to build custom validations to model properties based on an expression. However, we wanted to go a few steps further with this feature. Here is what we did:
- You can now build multiple expressions to validate a model property.
- The expressions are sortable to decide which must be executed first.
- Each expression can hold a custom message to preview to the end user when the given value is invalid.
- Validation errors (and their messages) can be caught/ fetched by an after_validation action. This feature can be very helpful for example in import events. When import lines aren’t imported (because some are invalid) you want to know why.
Advanced model property validations with their messages to preview and catch
We made a learn article about this new feature. Soon we will provide you with howto tutorials in which we explain this feature even more.