With this release we introduce a new API endpoint (/stats
) for the contract
owners to collect statistical information including the number of workspaces,
flows and the component used in the flows.
Use the following call: GET /v2/stats/workspaces?{contract_id}
, where the
contract_id
is the ID of your contract. Your contract ID is the alphanumeric
number found in your browser address-bar after the letter c/
and before /w
while
you are logged-into the platform.
Our platform stops flows in the limited workspaces. We describe this in our Contracts and Workspaces general article. With this release you will receive notification when the platform stops them. You can still login and restart your flows.
With this release we improved the behaviour of the branch creation and modification while working with the Content Based Router component. To avoid confusion and standardise the experience the following changes were made:
Current Node.js Sailor version - 2.6.24
With this release we introduce next sets of improvements to the Node.js Sailor, the base library used to compile any Node.js based component code during the platform deployments.
This particular update includes stability for large message (~50MB) processing through
the request-reply chain. If you intend to include your custom component in the
request-reply scenario, we highly recommend updating the Node.js Sailor to at
least 2.6.24
version.
Along with this new improvement the Request-Reply (HTTP-Reply) component is updated. We recommend using at least 1GB RAM memory on the HTTP-Reply component and at least 512MB RAM memory for each step in your request-reply chain.
Current Java Sailor version - 3.3.2
With this release we introduce next sets of improvements to the Java Sailor, the base library used to compile any Java based component code during the platform deployments.
With introduction of the the version 3.3.2
all errors in component
credential verification are shown in the UI as errors. Previously errors were shown
in the logs only.
With this release we standardised behaviour of the UI in the mapping fields. Some notable improvements are:
enum
information.As a part of the component code audit we updated the Node.js Sailor version to 2.6.24
in the following components: