Released: 2020-01-16
Introducing new mapper UI. This feature is still in beta. You can use the switcher in the menu to try it out:

Introducing Executions page where all the executions based on processed data are listed. You can access it via the Navigational menu:

Handlebars are not supported any more. You can only use "default_mapper_type":"jsonata" in your integration Flows.
+ sign in email address would crash API. Not any more.RFC Server trigger. It is a generic trigger which gives possibility to receive RFC calls from the SAP ECC platform.We upgraded 22 components to the latest Sailor version, to take advantage of the
new logger, as well as to the new Docker build type:
Released: 2020-02-13
You can now see all the logs from one workspace on the dedicated logs page, located near the executions page in analyze section of the navigational menu:

While the most important logs are seen on the executions page, we decided no to spam you with everything else, and created a special page for all the logs. The new page lists all the logs for all the flows in the current workspace. Here you can filter the list by flow name, time, log level or use in-built search to find the logs you were looking for. For more details check our logs page.
As a back-end to the logs page we are introducing a new API endpoint (still experimental) to request the same logs in the workspace. More about that in the Retrieve logs API endpoint section.
As a back-end to the logs page we have a new, still experimental API endpoint v2/logs.
You can use this endpoint to request the same logs you see in the new logs page.
Here is the list of filters you can use with v2/logs endpoint:
workspace_id(required) - The Workspace identifierflow_ids[] - Flow identifierfrom - Start Date of the period in ISO 8601 format (2020-01-12T14:50:42.215Z)to - End Date of the period in ISO 8601 format (2020-01-14T15:00:45.000Z)search - String to search in logs (searching string is wrapped by tag)offset - Number of items to skip from the beginning (defaults to 0)limit - Number of items to return (defaults is 100)levels[] - The logs level (1 - None, 10 - trace, 20 - debug, 30 - info, 40 - warn, 50 - error, 60 - fatal)For more information about the endpoint visit our API reference documentation.
You can now switch between Integrator & Developer modes in the new mapper without losing any data that you have entered. However, if the root of the JSONata expression is a function, switching to Integrator mode is not possible since the Integrator mode has no functions support.
For components, which use sailor version 2.6.0 and higher, you can now disable passthrough during the flow creation/editing via the UI:
.
Now you can use OAuth2 authentication method with the REST API component. Select
OAuth2 as credential type. There are four mandatory fields (client_Id,
client_secret, auth_uri, token_uri) and two optional (scopes and additional parameters).
component.json) had an empty triggers object it would have appeared in the triggers selection during the flow design but not usable at all. Now we will not show that empty trigger of yours, you are welcome.Get New and Updated S3 Objects (aka Files). Polling By Timestamp.Get filenames action now returns any number of files. It was limited to 1,000 before.Get filenames and Write actionsOAuth2 authentication strategy{'result': %message%}.Introducing OpenAPI component for the platform.
Make requestOAuth2 authentication strategyLookup Objects and Lookup Object (at most 1) actionsQuery action where the first response object was being sent multiple times instead of sending actual response objectsA major update for the component:
Query and Lookup ObjectsLookup Objects and Upsert actions to support binary attachmentsdocker build typeWe upgraded 9 components to the latest Sailor version, to take advantage of the
new logger, as well as to the new Docker build type:
Released: 2020-03-12
In the Flow UI you can now view and edit snapshot of the trigger. Snapshot management is accessed via Advanced Settings in Step summary:

Then you get to snapshot manager itself:

You can now use Advanced Settings section in Step Summary tab to configure prefetch.
Note: the changes will be applied after clicking the Finish step button.

There is now a limit that defines the maximum number of errors we list for a Flow. If the limit is reached, no new errors are listed for the given Flow anymore. This new limit will protect you from the “chatterbox” Flows that tend to spam too much.
New MAX_ERROR_RECORDS_COUNT environment variable was added. If the amount of
errors per Flow gets higher then MAX_ERROR_RECORDS_COUNT value, we remove old
error records and show corresponding notification in UI.
Also, we added a new k8s CronJob remove-excess-error-records. This job is
clearing oldest flow error records if they are exceeding limit. The default limit
is 1000 records per Flow, and is set by MAX_ERROR_RECORDS_COUNT environment variable.
Automatic conversion of raw XML files on Webhook is toggled in component.json
with consumesRawData flag. If true, then Webhook will not convert incoming data to JSON.
Added better tool-tips for mapping modes in the new mapper.


INTERNAL - Flow Suspended was added to the segment.io, so we can better track
Flows suspension process.
You can now configure step message prefetch count through the API. We added a
new prefetch field as a parameter to nodeConfig section of the /v2/flows
endpoint. The mapper-step gets the same prefetch as the previous step.
EXAMPLE:
"attributes": {
"nodes_config": {
"step_1": {
"prefetch": 4
}
}
}
}
The default number of logs displayed per page is 200. You can set this number to: 400, 600, 800 or 1000.
New emails are sent in case of events of the following scales:
elasticio-sailor-nodejs@2.6.4 is required).refresh_token are now marked as invalid.Create OrderLookup Object By ID to allow lookup of Orders By External IDGet Objects Polling Trigger for “Time stamp field to poll on”refresh_token will now be marked as invalidrefresh_token and emits an error in case it is not validlookup object actionLookup Objects ( at most 1 ) now works for date or date-time field types