We are introducing a new header for the flow designer page to maximise the screen real estate and separate the integration flow graph from the functional buttons.
The animation below shows all the functionality in one go.
We are introducing a new functionality to copy flows from one workspace to the another. You must have at least Integrator level access in both workspaces for this to work. The new copy flow functionality behaves the following way:
In our back-end we have introduced API endpoints to use with copy flow functionality. These endpoints are still in active development and should be regarded as experimental. Check our API-docs documentation pages for more details.
Introducing a new VPN Agent. It is using а VPN tunnel specifically configured to access any local resource in your local environment. It could be any local database or CRM to which you would rather restrict access from outside world but still need to query for a data. Agents are available to configure by visiting the Agents page as usual. The dedicated VPN Agents page has more details about this.
Starting from this release the old Local Agents will be deprecated. You can
still visit and configure your agents by removing the
/vpn part of the address
while visiting the VPN Agents page.
We are introducing a new functionality called Lightweight messages. The main idea of this functionality is to reduce the load of messaging queue by sending the Lightweight messages through it. By reducing the load on messaging queue we reduce the processing time significantly and reduce or prevent out of memory errors during the data exchange between the steps.
Our aim for this realisation was to make sure the large size messages and attachments bypass the messaging queue all together. Instead of passing large messages through messaging queue we introduced an internal service which would temporarily store large message and provide an ID of these messages instead. These IDs, in turn, get sent through the messaging queue - not the big chunks of data.
If the step requires stored data it communicates with the storage directly, not through the messaging queue.
The Lightweight messaging is already implemented at system level. If you would like to use this functionality you must update the sailor version in your components to Node.js Sailor to
2.6.14version and Java Sailor to at least
We continue our improvements and developments of the New Secrets Management
service. In this round we made great improvements authentication client (
creation process. Previously
auth-client creation was possible on tenant level
and only by system administration. In this release
auth-client creation was extended
auth-clientat workspace, contract and tenant level. This enables scopes according to the
auth-clientcreation and dependence. For example the tenant
auth-clientis visible and can be used in secret in all workspaces in this tenant and so on.
GET /v2/auth-clientsis introduced to query values. You will get results only when you have permission to view these
auth-clients. For example if you have only
WORKSPACE.AUTH_CLIENT.GETpermission you will only get workspace level
GET /v2/auth-clients/:idis introduced to query
auth-clientendpoint with specific IDs. The standard access permissions apply in this case as well.
auth-clientrecord on workspace, contract and tenant level.
Check our API-docs documentation pages) for more details.
2.6.14and Java Sailor
3.2.0versions which support the Lightweight messages functionality.
3.3.0version which supports the Custom Error Handler functionality.
In our second iteration of Custom Error Handler feature we have made improvements and added more functionality.
Component container has failed to starterrors as well.
c/in browser window.
The component has undergone major refactoring.