Skip to main content
Feedback

Integration Release Notes for July 2026

Platform Release

July 11 2026

For this release, Integration features and fixes are not in the Runtime Release.

New
We added these features
  • Removed account-level feature flags for the following features, making them available to all accounts.
    • Advanced Runtime Environment Extension Access on Settings > Features.
      (INT-18015)
    • Integration pack release progress indicator on the Integration Packs page.
      (INT-17779)
  • Enhanced the integration pack release workflow, allowing you to easily navigate while a release is in progress and get the status of the release progress. (INT-17724)
  • Added a timestamp for successful and failed integration pack releases, enabling you to track release events with greater visibility. (INT-17291)
  • Improved performance when you review large merge conflicts, enabling you to review and resolve merge conflicts more efficiently, even with thousands of conflicts. (INT-17755)
  • Added archive and unarchive functionality to the Global Variables management page, enabling you to manage the lifecycle of variables directly from the UI without needing to use the API. (INT-17159)
  • Added an "Archived" status column to the Global Variables Management page, so you can identify archived variables and filter the table view accordingly. A banner displays in the information panel for archived variables, preventing inadvertent edits to their details or values. (INT-17158)
  • Renamed the archive parameter to status in the GlobalVariable API. Possible values are archived or active. The status parameter is always returned in Get and Query responses, so you can identify archived variables and protect them from unintended modifications. (INT-17535)
  • Updated the GlobalVariable API to prevent the assignment or update of values to archived variables, ensuring data integrity and consistency. (INT-17510)
  • The GlobalVariable API blocks changes when a variable is archived, preventing unintended modifications to retired variables. You can still update the status of archived variables. (INT-17509)
  • You can delete merges stuck in various stages using the MergeRequest API, allowing you to resolve issues with stuck merges. (INT-16211)
  • You can delete branches stuck in an unavailable or non-ready state after a minimum wait time using the Boomi Platform and the Branch API. (INT-15680, INT-16212)
  • Accounts granted access to an MCS cloud can now share that cloud with their own sub-accounts. Cloud sharing is limited to a single level of sub-accounts. (INT-17397)
Fix
We fixed these issues
  • The warning message when deleting an index field from the document cache lookup now explicitly prompts you to save the affected configurations after deletion. This ensures no references to the deleted index remain. (INT-11117)
  • Fixed the EnvironmentExtensions API Update action to validate values against the integer data type. The UI now displays a warning message if an invalid value is provided, prompting you to correct it before saving. (INT-14524)
  • Invalid Global Variable references are no longer included in the GlobalVariableReferences section of the Component API response. (INT-17814)
  • You no longer see an unexpected error when you add an Agent step to a process if the account's root folder name contains an ampersand (&). All other special characters are unaffected. (INT-16440)
  • You can now tab through fields in the Connector Step and the Document property under Set Properties shape without clearing the Operation or Connector field values. This fix applies to all supported browsers on Windows and Mac. (INT-16049)
  • The Component API no longer returns a missing-attribute-type error when you create or update the connector type field under the tradingpartneraction tag for the trading partner component. (INT-18048)
  • The Preserve Spaces checkbox no longer appears in the XML Attributes section of the XML Profile component. The checkbox was incorrectly exposed after a recent XSD and UI update. Preserve Spaces behavior continues to be supported implicitly, so your existing XML profiles are unaffected. (INT-17834)