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:
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.
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.
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:
...
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.
Now the features from the Platformeco Cloud Studio v4.4.0 are available in the desktop version!
shouldWaitDefinitionFinish into Pause policy to control execution time: immediately or after definition endACKS and ENABLE_IDEMPOTENCE set to previous defaults