Skip to main content
Feedback

Integration Release Notes for September 2026

Platform Release

September 12 2026

New features

  • Introduced a runtime selector in the Agent Step configuration panel, letting you choose any available runtime to browse registered agents and use Agent Step in an Integration process without the previous blocking error. (INT-16551)

  • Added an optional checkbox to the Map JSON to Multipart Form Data MIME operation in the Data Process step that keeps parameter values on a single line, up to 998 characters, in compliance with RFC 5322. (INT-18017)

These features are not in the runtime release.

Enhancements

  • The following functionalities are coming to Workspaces as a future Early Access feature:

    • The ComponentMetadata API's Query operation will scope results to your default workspace when you don't specify a branch. You can also filter by a specific branch to scope results to its associated workspace, provided you have read access. (INT-18423)
    • The Component API Create operation will resolve the correct workspace automatically based on the branch you specify. If you don't specify a branch, it will use your working branch's workspace or the account's default branch's workspace instead. (INT-18421)
    • The Branch API Query operation will scope results to a specific workspace instead of the entire account. If you don't specify a workspace, the query will use your default workspace automatically. (INT-18409)
    note

    Refer to the Early Access page to view current programs and reserve your spot for this upcoming feature.

  • Enhanced the Agent step to support global variables in its side panel and the Agent Operation component, letting you configure these settings dynamically for more flexible, reusable agent-based processes. (INT-17331)

  • Added a warning before deleting a branch that has active child branches, explaining that deletion will orphan the children and make them unmergeable into the main branch. (INT-14984)

  • Added support for naming process schedules. You can enter a custom name in the schedule list and its details panel, making it easier to tell apart multiple schedules of the same type. (INT-17171)

  • Added a createdDate field to the IntegrationPackInstance REST and GraphQL APIs, so you can sort and identify installed integration packs by when they were created. (INT-17341)

These enhancements are not in the runtime release.

Fixes

  • Resolved an issue where a Dynamic Document Property (DDP) referenced in a business rule error message showed a null value instead of its correctly set value when the evaluated field was missing from the source profile. (INT-14207)

    This fix is in the runtime release.

  • Resolved an issue where saving an Agent Step configuration with a blank configuration name caused a generic error. Configuration Name is now a required field, so you can't save without entering a name. (INT-17711)

  • Resolved an issue where filtering by an invalid execution ID in Process Reporting now shows a message instead of an unexpected error. (INT-15488)

  • Resolved an issue where a Try/Catch decision step returned an incorrect result when comparing exception message strings due to trailing whitespace. (INT-12794)

  • Corrected the interval field validation for Day (1-14) and Hour (1-12) type schedules so it accepts values instead of silently resetting to 1. (INT-11536)

  • Resolved an issue where deleted Hub runtime attachments still appeared in the Runtime Filters on the Dashboard and Process Reporting pages. (INT-16434)

  • Resolved an issue where a database profile with a single field or a single parameter displayed duplicate entries after clicking Expand All under the Statement, Fields, or Parameters section. (INT-16035)

  • Resolved an issue where renaming a process in the main account and re-releasing the integration pack did not update the process name on the Process Reporting page and ExecutionRecord query API for sub-accounts. A new account-level feature flag, updateWrapperComponentNamesOnRelease, controls this update and is disabled by default. To enable this feature, contact your Boomi account representative. (INT-15339)

  • Resolved an issue where the Show Where Used filter did not display components and processes that directly reference the selected component. (INT-16926)

  • Resolved an issue where switching between runtimes in test mode did not update process property extension values, causing the previous runtime's values to persist. (INT-12335)

  • Resolved an issue where the Process Reporting page displayed duplicate process execution logs when paginating through results. Each log entry now appears only once. (INT-16127)

  • Resolved an issue where the looping option for an XML profile element automatically changes to "Unique" from "Occurrence" when navigating between tabs, ensuring the selected looping option is retained as expected. (INT-550)

  • Resolved the AI Agent's Component Diff feature to correctly handle map functions with Simple Lookup keys or values starting with leading zeros, enabling you to accurately compare component versions with such data. (INT-14893)

  • Resolved an issue where updating a global variable caused X12 EDI trading partner listener processes to fail at the Start step.(INT-18435)

  • Resolved an issue where text fields in generic connector operations for SDK-based connectors didn't accept global variables. (INT-18404)

  • Resolved an issue where sorting by a tracked field column in the Execution Results view produced incorrect row order. Sorting now works correctly for Character, Number, and Date/Time tracked fields. (INT-18086)

  • Resolved an issue where copying and pasting a global variable in a text form row duplicated the value and added extra spacing. (INT-17675)

  • Resolved an issue in the Map step where exporting mappings to Excel produced incorrect results when cached data was present in the source profile. Non-cached elements now export with accurate mappings and no duplicate entries. (INT-1653)

    These fixes are not in the runtime release.

On this Page