2024 release notes

This update enhances the performance and responsiveness of the user profile display, offering a more intuitive and efficient way to manage and view profile details.

The transition to React modernizes the user interface and lays the foundation for future enhancements and optimizations, providing users with a more seamless and enjoyable profile management experience.

The navigation within the Integrations platform now displays page titles in the browser history for all React-powered pages.

Users can track their browsing history and identify specific pages by incorporating descriptive titles for each page.

This enhancement allows users to retry errors seamlessly and provides a clear hint stating that the flow needs to be active for the retry function to work.

This convenient feature allows users to manage and troubleshoot errors, promoting a more user-friendly and efficient workflow within the platform.

Enhance user visibility and control over flow operations by showcasing the live status of containers on the “Flow Queues” page.

With this enhancement, users can now monitor the actual status of flows in real time, empowering them with valuable insights into ongoing processes.

Since this trigger is initiated by another flow, displaying the CRON tab becomes irrelevant and can confuse.

By removing this tab, users benefit from a more intuitive and streamlined interface, ensuring that flow configuration remains clear and concise.

This enhancement ensures that users receive more precise and informative explanations of errors directly on the UI, enabling them to identify and address issues quickly.

By utilizing a separate Redis cluster for Webhook quotas, potential failures are minimized, ensuring uninterrupted service and improved performance.

This approach not only safeguards against quota-related issues but also enhances the scalability and stability of the system, providing users with a more dependable and resilient Webhook quota service within the platform.

Initial component release.

Initial component release*.

Improved the flow name visibility in the filter dropdowns on the Executions, Containers, and Logs pages. With this release, when hovering over flow names in the filter dropdowns, the full flow name presents as a tool-tip if it is too long to display in the dropdown.

This provides quicker access to information, facilitating quicker understanding and navigation within the platform, and making it easier to identify and select specific flows for specific tasks.

The new Exports dropdown menu offers users two options: Export Flow(s) and Export to a Recipe.

When Export Flow(s) is selected, users can choose one or multiple flows and export them simultaneously to any available contract and workspace as flow drafts.

This enables users to manage and export multiple flows. This, in turn, makes it possible to better optimize workflows and boost productivity.

More information about this feature is available in the core documentation.

Enhanced data representation in the JSONataView viewclass with introducing a label field display. Users can now access and view the contents of the label field within JSONataView, as described in the component.json file.

This allows for more precise data visualization and interpretation within the viewclass. It enables users to better understand and analyze the label field content within the JSONataView viewclass.

A new API endpoint https://api.au.connect.squiz.cloud/docs/v2#/flows/delete_flows_subscription allows users to unsubscribe either from flow errors across all their flows or flow errors within a specific workspace.

This allows integrators to more efficiently manage error notifications.

Users can now view the Default label associated with a branch of the router component directly on the flow queue page.

This update provides users quicker access to essential information, facilitating quicker understanding and more efficient management of the routing logic within the flow queue.

When the quota for Webhook requests is exceeded, the Webhook URL now responds with a 429 Too Many Requests status code.

Users interacting with the credential fields of the Webhook component will now go through validation to identify unsupported characters.

If unsupported characters are detected, an error message — Disallowed symbol(s) — presents. This helps ensure data integrity and safeguards against unauthorized access.

A checkbox was added next to the filters that enables hiding executions without messages.

Checking this box removes empty executions from view.

This restricts the display to executions with messages, improving Execution page usability and, potentially, improving the efficiency of flow monitoring and analysis.

Unprocessed expiration errors from Kubernetes are now handled.

A dedicated metric tracks and logs restarts associated with unprocessed expiration errors. The logs provide data for measuring and investigating system stability and performance.

A new, more memory-efficient, library has been deployed, replacing the old library.

The new library reduces UI memory usage. In most circumstances, the result is a more responsive UI.

In testing, the new library reduced freezes to zero and provided a smooth workflow, even when working with large sample datasets

Initial component release.

Initial component release

Initial component release.

Initial component release.

Initial component release

Initial component release

Initial component release

A noteworthy enhancement in this version is the introduction of an authorization mechanism. This mechanism involves the use of credentials, which are available in four distinct types:

Initial component release

Initial component release.

Initial component release.