As we announced in the release 21.47, we are ready to present you a new even more understandable and intuitive design for Flows page. We are trying to unify our platform design. The first improvements are more convenient filtering and an easier way to edit a flow. Now you just need to click on “Edit” button and you are automatically redirect to the Flow Designer page with already created draft (Note: if a draft for a flow already exists, it will not be overwritten). We added the “Stop” button for the flow in suspended state. So you have the option to resume the flow and keep the messages in queues, or stop the flow and clear the queues. Here you can see what changes have been made:
Picture shows the flow card changes.
We also improved flow card menu:
Picture shows the flow card menu changes.
For more informations on flow management please visit our documentation page.
We decided to make some flow step configuring panel design changes. Now the step configuration menu is fixed under the flow panel, and it will also be tied to the specific step that you are editing. This will be especially useful in the case of “wide” flows, where you will always see exactly the step that you are configuring.
In order to speed up the work of the flow draft page, we decided to improve a caching system. We added
if-none-match by default header to the API proxy mechanism to improve responses caching on the client-side.
For more informations on
if-none-matchheader visit this page
We constantly improve different aspects of HELM3 deployments in collaborations with our partners. This section lists updates and improvements done in this round.
global.apiDocsImage from the helm values and set platform version for api-docs image.
From now you don’t need to specify manually api-docs image commit hash in k8s-clusters. When you deploy any platform version you can be sure that api-docs corresponds to a given platform release.