← BACK
PRODUCT NEWS
2024-04-24 20:32

Important releases Q1 2024

Superagent Connector 5.5.0

Bug-fixes:

  • Fixed problem with URL encoding when there was non-ASCII characters.

Ftp Connector 4.3.4

Bug-fixes:

  • Validate client connection for FTP service before using it.

Jsonschema Policy 4.7.2

Bug-fixes:

  • Reference $ref now resolves correctly from file schema when configured via file

IMAP Connector 1.3.0

Features:

  • Added the ability to specify a query in the Search policy in UI mode

Ftp Connector 4.3.6

Bug-fixes:

  • File format representation in SFTP listAsync method

Core 3.42.0

Features:

  • Added workflow information and context from config to initial context at workflow startup

Postgres Connector 2.2.3

Bug-fixes:

  • Fixed the problem of studio crashing with an error when adding transaction and rollback policies to flow.

Delay Policy 2.1.1

Bug-fixes:

  • Fixed an error populateTemplateString is not a function.

❗ Scheduler module 1.2.0

Features:

  • Added job health status to scheduler UI: coloured circle is shown next to each job at the jobs list representing it's health status. The status is calculated based on last five executions results, calculation algorithm:
    • If all five executions ended up with success, the circle will be green.
    • If at least one of the last five executions has failed then the circle will be yellow.
    • If all five executions are failed then the circle will be red.

Control Center 0.8.0

Features:

  • Added a page leading to Control Plane Role Management

Bug-fixes:

  • Correct display of the environments drop-down list

❗ Channel Loader 6.8.0

Features:

  • Added tools entity. Added ability to run tools. This feature will be available in new Cloud Studio soon.

Bug-fixes:

  • Fixed incorrect handling or proceed-on-error property for loaders
  • Now folder and filename renamed when definition or shared flow name was changed

❗❗ Platformeco Cloud Studio 4.4.0

Features:

  • The new types of policies – sequence, branches, and loop – are now available.

Sequence policy

There are times when you do not want one statement to take effect unless another one completes.The way to be sure that either all action occur or neither action occurs is to use a transaction. A transaction is a set of one or more statements that is executed as a unit, so either all of the statements are executed, or none of the statements is executed. There are also cases necessity of use streams. A stream is opened at the beginning of the policy, and then the server sends data packets as part of the stream. The client does some processing for each received packet until the server says that the stream is finished. Sequence policy is designed for such transactions and streams cases. For example, it can be use for transactions to DB or for gRPC streams.

Sequence policy group has a rectangular outline border indicating a sequence subflow. It can be minimized, expanded, and deleted. A small icon in the block is indicating the type of the policy.

These Sequence Policies are now available:

  • KafkaRead – a policy that allows users to define the number of messages received per request, optimizing data flow and workload management
  • PG Transaction – a policy that starts a PostgreSQL transaction
  • JDBCTransaction – a policy that starts a JDBC transaction

Loop policy

While Policy is now supported. The policy that provides a subflow is executed until a specified condition is met or an exit statement is reached. It can be use for implementing For, While, and Do-While loops, etc. Loop subflow has a dashed line. Thee loop subflow can be minimized, expanded, and deleted. A small icon in the block is indicating the type of the policy.

Branches policy

The policy that provides branching the flow either for parallel execution or execute the branch based on the particular condition. It can be use for implementing Try/Catch/Finally policy, etc. Branch policies can be either with a static amount of branches, or with a dynamic one.

If the amount is static, the amount of branches is indicated in the YAML, when adding a policy to the flow, you immediately gets the right amount of branches. If the amount is dynamic, then the plus button appears on the hover, for the convenience of adding branches. By hovering the edge a delete button appears on the branch, by clicking on it, a confirm appears. The branches subflow can be minimized, expanded, and deleted. A small icon in the block is indicating the type of the policy.

New policies development

To create a custom policy of the specific type, add to the YAML file of the policy the type of it on the first line:

type: sequence # or branches or loop
info:
    ...
properties:
    ...

Implemented styles for core policy states

We are excited to introduce a new feature in this release that enhances error handling within our platform. Now, if an error occurs while executing a definition/shared flow in a loop or branch of a core policy, it will be displayed in the state style of the policy itself. This improvement enables users to easily navigate within flows and quicker identify errors that occurred during execution. We believe this enhancement will streamline the debugging process and improve overall user experience.

❗❗ Studio Desktop v2.3.0

Now the features from the Platformeco Cloud Studio v4.4.0 are available in the desktop version!

Features:

  • More than 100 improvements and fixes related to tracing, sharedflows, sidebar, data models, variables repository, search, drag&drop, flow etc.

Telegram Connector 3.3.0

Features:

  • Change the format of the Text field in the Send message policy to format: template

Fastify Connector 3.7.3

Bug-fixes:

  • Fixed documentation tags being reset during conversion

Cloud Manager 11.8.0

Features:

  • Added russian localization to main releases which work with Control Plane

Kafka Satellite 1.9.0

Features:

  • Transmit current version as initialization result

Bug-fixes:

  • Process deferred commits (received and stored in internal queue) on сonsumer stop, it should decrease message duplication in restart or pause cases

Kafka Connector 5.4.0

Features:

  • Added flag shouldWaitDefinitionFinish into Pause policy to control execution time: immediately or after definition end

Channel Loader 6.8.2

Bug-fixes:

  • While Loop policy merges with foreach policy in sidebar
  • Fix workflow nodes and activities filenames
  • Removes part of telemetry config because of propagation option

Channel Loader 6.9.0

Features:

  • Add workflow to sidebar in definitions and shared flows

Platformeco Core 3.43.0

Features:

  • Support Proceed-On-Error property for workflow nodes, activities and child workflows
  • Support Workflow block in definitions and shared flows
  • Handle retries and timeout options for staring workflow

Workflows Policies 1.2.0

Features:

  • Add Retry and Timeout options for startWorkflow policy

Fastify Connector 3.8.0

Bug-fixes:

  • Fixed paths when converting settings to documentation and vice-versa for openapi2 and openapi3

Kafka Connector 5.5.0

Features:

  • Added warning output when one connector reads 2 or more topics. "Connector=[${connectorTitle}] reads more than one topics in the definitions=[${definitions}]"

Cloud Manager 11.9.0

Features:

  • Added creation of a sidecar temporal container along with the session.

Bug-fixes:

  • Now the table behaves the same in Russian and English (equal rows). For this purpose we made the title fixed and changed some translations.
  • Kafka env variables previously came incomplete and only from one container. Now it is a merged value from the sattelite and nats container.

Cloud Manager 10.5.1

Bug-fixes:

  • Now the table behaves the same in Russian and English (equal rows). For this purpose we made the title fixed and changed some translations.
  • Kafka env variables previously came incomplete and only from one container. Now it is a merged value from the sattelite and nats container.

JDBC Satellite 4.5.0

Features:

  • Update dependency HikariCP to 5.1.0 (main library to manage connection pool)

Kafka Satellite 1.9.0

Bug-fixes:

  • Fixed inconsistencies after client upgradation: ACKS and ENABLE_IDEMPOTENCE set to previous defaults