December

Release notes 12/03/2024

New use case: Reprocessing strategy in event-driven integrations

Our new use case guides you through implementing a reprocessing strategy in event-driven architectures to enhance reliability by preventing data loss, reducing manual effort, and improving operational efficiency.

Explore this and more hands-on content in the Use Cases in Action section of the Documentation Portal.

Documentation

Improvements and bugs

Improvements

  • New navigation experience in Groups: We have enhanced the browsing and search functionality for Groups in the Administration section of the Digibee Integration Platform.

Bugs

  • Redeploy for multi-instance pipelines: We fixed the bug in the redeployment process for multi-instance pipelines, ensuring proper handling when a new version is detected as already running on another instance.

  • Multi-instance pipelines are not displayed on Pipeline Metrics: We fixed the bug that caused multi-instance pipelines to not appear on the Pipeline Metrics page.

  • Errors in the replica usage count on the Pipeline Metrics page: We fixed a bug where the number of executed metrics displayed when running pipeline tests differed from the available metrics shown on the page .

  • Pagination error on the Accounts page: We fixed the bug that caused a pagination error on the Accounts page.

  • Pipeline list missing on the Account edit screen: We fixed a bug during account editing where the pipeline list disappeared when clicking to advance to the next page.

  • Pipelines with a custom account not listed as associated: We fixed a bug that prevented pipelines using custom accounts from appearing in the Associated pipelines section.

  • Pipelines with accounts in triggers not listed as associated: We fixed a bug where pipelines using a trigger linked to an unlisted account were missing from the Accounts sidesheet.

  • Do While connector in Debug mode: We fixed a bug where the iteration steps of the Do While connector could not be verified in Debug mode when multiple Do While connectors were present in the flow.

  • Multipart calls in the REST connector: We fixed the bug where the REST V2 connector did not maintain the order of fields when the Content-type header was set to multipart/form-data, impacting requests to services that required a specific field order.

  • JOLT connector and decimal numbers: We fixed the bug where the JOLT V2 connector converted decimal numbers to scientific notation when pipelines were deployed.

Last updated