Jump to
Product Updates
v24.13 v24.09 v24.05 v24.01 v23.48 v23.44 v23.39 v23.31 v23.27 v23.27.1 v23.24 v23.19 v23.19.1 v23.14 v23.14.1 v23.12 v23.10 v23.08 v23.06 v23.04 v23.02 v22.52 v22.50 v22.48 v22.46 v22.44 v22.42 v22.40 v22.38 v22.36 v22.34 v22.32 v22.30 v22.28 v22.26 v22.24 v22.22 v22.20 v22.18.1 v22.16 v22.14 v22.12 v22.10 v22.08 v22.06 v22.02 v21.51 v21.49 v21.47 v21.45 v21.43 v21.41 v21.39 v21.37 v21.35 v21.33 v21.31 v21.27 v21.23 v21.19 v21.14 v21.10 v21.06 v21.02 v20.51 v20.47 v20.43 v20.39 v20.35 v20.31 v20.27 v20.23 v20.19 v20.15 v20.11 v20.07 v20.03
Updated on

Product Update - v22.04

Details of the product update v22.04 from 27th of January 2022.

Features

Announcement: New design for Step configuration

We would like to inform you all about the impending roll-out of the new Integration flow Step configuration page during our next 22.06 release (10th of February 2022). Our OEM customers will receive the detailed explanation of changes in advance.

Here is the difference of already configured integration step showing the summary page:

New Step Designer

We would like to draw your attention to the impending changes:

  1. The upper panel showing the progress will change into a vertical sliding structure. You can expand each section vertically.
  2. Here you have information about already configured component like the component name, developer team, component version, used function and the ID of credential.
  3. Shows buttons you can use to expand or collapse all sections at once.

Next screenshot shows details of a component configuration view where not all sections are completed:

Details of step configuration

Here you can see the difference between already configured sections (shown in green), next section to configure (filled grey) and the other sections (hollow grey) which will not be possible to configure unless the previous section is completed.

Next screenshot shows details of a component configuration view where the Jsonata field has an incorrect entry:

Details of step configuration with error

Improvements and Updates

The release 22.04 includes lot’s of work under the hood. Our team is working to improve and refactor some of the core microservices.

Component deployments via Docker images

In our 22.02 release view announced our intention to find a new path for component deployments. The one which would not require direct involvement of our support.

With this release we are happy to let you know that we have made significant progress in identifying the reliable mechanism and testing our first node.js and Java component deployments using the automated build processes from CircleCI.

Here is the workflow we have already in place:

  1. New version (tag) is created in the GitHub component repository and the release is published.
  2. CircleCI build process uses appbuilder + apprunner images.
  3. Docker image of the component is built with the tag version and submitted into the Dockerhub.
  4. An additional latest version is created at Dockerhub side each time code is updated.

Stay tuned for our next steps.

News in this section are for our customers who use OEM version of the elastic.io platform.

Quota for flow count

In the release 21.45 we announced about the new quota feature capability to limit flow counts per workspace, contract and tenant. To apply this quota you must have either the Service Account or Quota Manager credentials.

  • If you host your own installation (on-premises case) then you already have these credentials.
  • If you have an OEM tenant on elastic.io hosted clusters talk to us for the quota management.

We have now a dedicated documentation page about the Flow Count Limit.

Components

Bigcommerce Component 1.0.0 and 1.1.0

  • ADDED Create action
  • ADDED Update action
  • ADDED Delete action
  • ADDED Lookup Object by ID action
  • ADDED Lookup Objects by multiple filters action
  • ADDED Make Raw Request action

Utility Component 1.4.0

  • ADDED Log Message action
  • ADDED Create JSON Patch action
  • ADDED Apply JSON Patch action
  • UPDATED dependencies