NOTE: From this release we have adopted new release numbering format based on year and week of the release -
YYare the last two digits of the year, and
WWis the number of the week in that year. Following this template, our current release is
You can now retry failed messages using the new feature called Retry. Any error emitted by a component can be retried if the flow is active. Error or success entry appears in the current Runlog execution. Feature details can be found here:
Also, now you can filter mapping view to see mandatory fields and hide optional fields:
You can now disable the passthrough for a selected flow step using an API call to the following endpoint:
NOTE When the passthrough is disabled for a step, the platform would reset all the data from the previous steps and start again collecting the data from the steps from that step only.
This feature is available via an API call only. More details here.
Order of fields in component descriptor
Now you can configure the order of fields in
component.json using the new numeric key
- output metadata
- action/trigger order
- action/trigger on recipe activation page
- credentials on recipe activation page
For more details read the component descriptor ordering fields document.
Custom scripts for individual tenants
Additionally, custom scripts for individual tenants can run on every page before authorization:
- Login pages
- Forgot password pages
- Register pages
- Reset password pages
- Invite page
- Component environment variables can have global visibility again.
- The deprecated links
tenant.linksin the tenant description body are no longer supported.