We introduce a new possibility to obtain the debug and one-time executions logs
straight from the logs window. You can choose to Download the logs directly to your
computer and the system will give you a time-stamped *.log
file or you can choose
Copy to clipboard to paste the logs where you need. The small animation below shows
these options.
With this release we spent considerable time to streamline and improve the platform UI pages. For example the executions page is now more responsive and the new executions show much faster than before. By our initial estimate it loads 20 to 30% faster. We also load next and previous executions pages asynchronously to improve the first page loading speed.
The mapper UI received a particular attention where we improved the usability of multiple features explained in the following subsections.
While using the dynamically selectable fields from third party sources you might encounter situations when no metadata is returned. In this cases we will show the following warning text to text:
Unfortunately the service behind the component did not provide any options for the given credentials. This is not necessarily an error. Please check whether there are data for the given credential and retrieve the options again by clicking on the Reload icon on the right side of the drop-down element.
All text-input fields now grow with the content. When the you have an input longer than 4 to 5 lines, a new vertical resize selector in the right bottom corner of the field appears. You can use it to extend the field for your viewing convenience.
You can scroll to see all the content of mapped fields in any saved flow versions. The scroll-bars show not only the input fields but besides the mapping results too.
You can now switch between Integrator and Developer modes and edit without a problem
while using any object
type in your mapping.
We are constantly improving Sailor versions for Node.js and Java programming languages. In this round we addressed edge cases when trigger and action functions might output sensitive data while processing error stacks. Here are the most recent versions:
2.6.18
3.3.1
To address certain 3rd party OAuth2 provider unique setups we introduced default
token_expires_in
parameter with 1 hour interval. The background of the problem
came from the cases when the external systems (e.g. Salesforce) would not return
token_expires_in
for the auth-client
calls.
Now any authentication client without expieres_in
parameter receives a default
token_expires_in
parameter with 1 hour value. This value will propagate to the
connected secrets as well. The API documentation was updated accordingly.
Authentication failed by authSource
.2.6.18
.batching-library
version.2.6.18
.2.6.18
.component.json
which caused en error in drop-down.2.6.18
.emit
was called without await
.2.6.18
.As a part of the annual component code audit for a possibility of sensitive data exposing we checked and updated the following component codes and the dependencies:
3.3.1
.