Jump to
Product Updates
v25.43 v25.42 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.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.04 v22.02 v21.51 v21.49 v21.47 v21.45 v21.43 v21.41 v21.39 v21.37 v21.35 v21.33 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 - v21.31

Details of the product update v21.31 from 7th of August 2021.

Features

Regenerate your REST API Key

The 21.31 introduced a new opportunity to regenerate your personal API key you use to authenticate your calls with the platform REST API.

You have two options, either using a new Generate new API Key button in your profile page or using a HTTP POST to the new API endpoint /v2/users/me/generate-api-key. In both cases the platform will generate a new API Key and store it in the Database

Please Note Generating a new API key will replace the existing API key. If a new API key is generated, then API calls made with the old API key will fail.

Two-factor Authentication

We introduce two-factor (2FA) login authentication to provide an additional layer of security. We use Google Authenticator for the 2FA. If the feature is enabled in the tenant then you can enable it for your account following the instructions in the profile page.

Component Whitelisting

With the platform 21.31 version we introduce a new feature called Component Whitelisting. In verbatim this means we can enable or disable certain integration components in each contract based on the list of components - the Component Whitelist. If the component whitelist is enabled in the tenant the following rules would apply in each contract:

  • You have access to all components available in your tenant while working in the developer (limited) workspaces.
  • You can only build integration flows using the available components (whitelisted components) in your production workspaces. Not included components would not show in your production workspaces while building an integration flow.
  • You can not export an integration flow from the developer workspace to production workspace if the flow contains a component not included in the whitelist.
  • You can not create a recipe with a contract level access when the recipe uses a component not included in the whitelisted components for the contract.
  • The developer workspace will not be converted to a production workspace in case when at least one step of one flow in your developer workspace uses not whitelisted component.
  • All native components from your contract with team access level would still be available in your production workspaces.

Remove pending Contract invites

With platform 21.31 we added support for deleting pending invitations to contracts using UI and API.

Now you can delete the user invitation by visiting Members section of the Contract Settings, scrolling down to find the list of Pending Members and clicking to delete. Check the following documentation page for more details.

You can also delete the invitation using the API call.

Fixed Bugs

  • Addressed the problem when it was not possible to join the Contract via invitation letter in case login with OIDC (Login using Google credentials)
  • Fixed UI bug Invalid '0' value in the required fields with type 'number'.
  • Addressed and standardised Maester’s Redis. Sometimes it used to leave incomplete object keys and Maester would not regard this as problem.

Components

Splitter component 1.2.1

  • ADDED support of maester storage in Re-assembled message action (maester-client library 3.3.0)

CSV component 3.0.0

We released a new version of the component which is not backwards compatible. Users are encouraged to investigate the CSV component documentation to learn about the new component.

The component will not be deployed on top of the old component repository, you can keep using the old component. At some stage we will deprecate the old one. The new component is available as csv-v3 component in your components list.

  • ADDED new following actions:
    • Read CSV attachment
    • Create CSV From Message Stream
    • Create CSV From JSON Array
  • DELETED the following functions:
    • Read CSV attachment trigger
    • Write CSV attachment
    • Write CSV attachment from JSON Array
    • Write CSV attachment from JSON Object
    • Read CSV file from URL

id-linking-component 1.0.1

  • UPDATED to sailor version 2.6.26
  • UPDATED to Maester client library version 3.0.0

Delta Detection Component 2.0.1

  • UPDATED to Maester-client version 3.3.0

Google PubSub component 1.7.3

  • FIXED the bug with not-awaited emits and endless cycle

Maester component 1.0.0

We introduce new component for working with platform native object storage called Maester.

  • ADDED the following actions:
    • Delete Object
    • Lookup Object (at most one)
    • Lookup Objects
    • Upsert Object

Utility Component 1.3.0

  • ADDED new action: Delay
  • UPDATED the sailor version to 2.6.26 and build type to docker