Jump to
Product Updates
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.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.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.52

Details of the product update v22.52 from 29th of December 2022.

Features

Additing tenant roles

We have changed the name of permission tenants.tenant.edit_roles to global.tenant.edit_roles.

Now PATCH /v2/tenants/:tenantId/roles allows to create a new role with permissions in a tenant scope. We have also updated API endpoint PATCH /v2/tenants/{tenant_id}/members/{user_id} which allows granting any role from the tenant’s scope to any user. The permission tenants.user.generate_one_time_token can be granted to any user inside the tenant.

Abbility to read recipies by SERVICE_ACCOUNT

Our goal is to make easy-to-use recipes. In a recent release 22.48, we have already begun some improvements in this direction. Now we are introducing a new permissionGLOBAL.RECIPE.GET to view all recipes based on the permission’s scope and provide the new permission to SERVICE_ACCOUNT with the Global level. This is the first step in the development of a new feature, in which the new role of the superuser will allow you to review and approve recipes, as well as to change their level up to tenant or global if necessary.

Please Note: All updates related to the API are detailed here.

Scalable Redis Cluster

We are working on the Redis Cluster improvements. We made Redis Cluster scalable according to the load increases. Please follow the instruction below to deploy the cluster:

  1. Deploy the secrets chart first.
  2. Deploy bitnami/redis-cluster chart. Ask support for the config.
  3. Wait until all 3 instances of redis-cluster are up and running.
  4. Make a regular deployment.

New secrets config variable:

REDIS_CLUSTER_PASSWORD - the password of redis cluster instances.

Fixed bugs

  • FIXED bug, where additional fields can’t be saved in faceless credentials.
  • FIXED bug, where the step number was duplicated. Now you can change the name of the step, but the step number will remain displayed.
  • FIXED bug with red Router branch indicator. Now if you have unconfigured Router branch its panel has a red border:

CBR fixed bug

Components

NetSuite component 3.0.0

  • Breaking change - User credentials authentication mechanism has been removed. As it is no more supported by Netsuite SOAP API
  • UPDATED API version to 2022.1
  • UPDATED the Sailor library version to 3.4.0
  • ADDED required dependencies to component.json fields
  • ADDED Circle.ci job to build and push images to Docker Hub

SAP ByDesign component 2.1.4

  • UPDATED the Sailor library version to 3.4.0

Google Cloud Storage component 1.0.0

  • ADDED Make Raw Request Action
  • ADDED Upload file Action
  • ADDED Download file Action
  • ADDED Delete file Action

Router component 1.0.1

  • UPDATED jsonata-moment library to 1.1.5 in order to support Jsonata 1.8.6
  • UPDATED the Sailor library version to 2.7.1