Jump to
Product Updates
v25.36 v25.23 v25.20 v25.14 v25.10 v25.06 v24.50 v24.45 v24.40 v24.36 v24.27 v24.23 v24.17 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.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.04 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.34

Details of the product update v22.34 from 25th of August 2022.

Improvements and Updates

Informative error messaging for invalid SSH key entries

When we introduced support for newest SSH versions for the user SSH keys used to deploy components, we deprecated the old ssh-dss types. If users enter an unsupported or incorrect SSH the user interface now displays an informative error message instead of simply disabling the ‘Save’ button.

SSH Key screen in case of Error

Deployment of Externally Build Dockers

This capability will provide an alternative to Git push deployment of user developed components and is of interest to enterprise clients wishing to condense entire integration flows into single custom components and maintain control at the docker level.

At this earliest stages we lay our groundwork by updating the component commons and api to support components pull from external docker registries. The following new attributes were added:

  • docker_registry object into the HTTP POST call to /v2/teams/
    • attributes.docker_registry.uri - Docker Registry URI
    • attributes.docker_registry.credentials - Docker Registry credentials
  • docker_repo_name and docker_target_tag in the POST HTTP call to /v2/components (can be set if its team has docker_registry object)
    • attributes.docker_repo_name - String representing component’s name in docker registry. Available only if team supports docker registry
    • attributes.docker_target_tag - String representing component’s tag in docker registry. Available only if team supports docker registry

Please note, as of this stage these attributes have no functionality attached to them.

Fixed bugs

  • Fixed the bug when an HTTP POST to /v2/workspaces/:id/secrets/:id/refresh endpoint would return outdated access_token instead of the newly refreshed value.

Components

Qualtrics component 1.0.0

  • ADDED Get New and Updated Objects polling trigger
  • ADDED Make Raw Request action
  • ADDED Upsert Object action
  • ADDED Generate Custom Distribution Link action
  • ADDED Getting Survey Responses action
  • ADDED Lookup Object (at most one) action

Google Spreadsheets V2 component 1.0.1

  • IMPROVED the component behavior in case of 429 status code. Now it will retry the messages with an exponential backoff.
  • IMPROVED the component behavior in case of 5xx errors. The messages will be retried with an exponential backoff as well.

SFTP component 1.5.1

  • UPDATED component the component-commons-library to the version 3.0.1

SugarCRM component 1.1.6

  • ADDED email1 and email2 fields for metadata of Contacts module in the Upsert Action
  • UPDATED elasticio-sailor-nodejs to v2.6.29

Shopware V6 component 1.0.0

  • ADDED Make Raw Request Action

Request-Reply component 1.2.5

  • UPDATED the maester-client library version to 4.0.2
  • UPDATED the component-commons-library to the version 3.0.1

Zoho Subscription component 2.0.0

  • UPGRADED authentication mechanism to OAuth 2.0 and migrated to the Secrets service
  • UPDATED the sailor library to version 2.6.29
  • UPDATED build time dependencies