Skip to main content
Feedback

Integration Release Notes for November 2026

Updated 

Platform Release

14 November 2026

New Features

  • Introduced JSON profile support in Data Map Extensions, so you can map JSON fields in Environment Extensions and apply them at runtime. (INT-17970)

    This feature is in the runtime release.

Enhancements

  • Updated the Agent step to set Runtime Type automatically when you generate a configuration. Agents on a Flex Runtime use the Common setting and do not require a Platform API token. (RAS-989)

  • Added a 10,000 record limit to the Documents page in Process Reporting. Refine your filters or use the Platform API to retrieve the full set. Improved document record searching performance in the Platform API. (INT-18934, INT-16442)

  • Enhanced the GenericConnectorRecord API to retrieve generic connector records across multiple executions in a single query. You no longer need to query by one execution ID at a time. (INT-19139)

  • Enhanced the GenericConnectorRecord API to let you search for executions across connector-specific tracked fields without requiring an execution ID. (INT-18873)

  • Changed process library installation to use the dependencies captured at publish time instead of the source account's live branch. Installed process libraries now match the exact dependencies from publish. (INT-18940)

  • Enhanced branch creation to associate every new branch with a workspace. If you don't specify one, Boomi uses your default workspace. (INT-18267)

  • Improved branch and merge request processing so one hung merge no longer blocks other merges. Stalled merges now time out, retry, and move to a failed state when retries run out. (INT-19175)

  • Added a Select All checkbox to each extensible property list, including Connection Settings, Operation Settings, Partner Settings, Process Properties, Cross Reference, and PGP, in the Process Extensions dialog, so you can select or clear all properties at once. (INT-18542)

    These features are not in the runtime release.

Fixes

  • Resolved an issue where the runtime used the wrong Groovy cache directory after the first script compiled, causing unexpected char: 0x0 @ line 1, column 5 errors. (INT-19207)

    note

    This defect affected only users who took the 26.09.4 runtime patch and did not set the container property com.boomi.container.scripting.<language>.reuseEngine to true.

  • Resolved an issue where Groovy script engine instances built up in memory instead of being released after execution, causing memory use to grow without limit on basic runtimes and runtime clusters. (INT-17748)

    To enable this fix, set the container property, com.boomi.container.scripting.<language>.reuseEngine to true. <language> can be groovy or groovy2.

    note

    This fix was initially released in the 26.09.4 runtime patch.

    These fixes are in the runtime release.

  • Resolved an issue where canceling the override confirmation prompt on an Environment Extensions Cross Reference still saved overrideValues as false and unchecked previously selected rows. The Override checkbox now retains its correct state when you cancel the prompt. (INT-17194)

  • Resolved an issue where the Bridge Execution icon did not display in dark mode. The icon now has sufficient contrast. (INT-17673)

  • Resolved an issue where the IFS connector ignored a Dynamic Document Property override when you turned on Global Variables, returning no data. (INT-18887)

  • Resolved an issue where the Destination field in the JMS V2 connector operation didn't support global variables. The global variable dropdown now appears correctly when you enter $V{ in this field. (INT-18706)

  • Resolved an issue where clearing the Map Script selection in a map function did not persist after saving. The selected value reappeared when you reopened the function. (INT-16145)

  • Resolved an issue where Process Reporting failed to load executions with a date mismatch in the execution ID and showed a generic error. Boomi now shows a message that explains the mismatch. (INT-13625)

  • Resolved an issue where the XML profile Looping option for a child element switched from Occurrence to Unique when you moved between the Types and Data Elements tabs. The option now keeps your selected value. (INT-550)

  • Resolved an issue where the Extensions dialog did not list Operation Settings extensions for listener-started processes created through the Platform API. The Operation Settings drop-down no longer shows "None Available" when valid overrides exist. (INT-17954)

  • Resolved an issue where updating a listener process through the Component API dropped its start step properties, causing the Deployed Processes page to classify it as schedulable. (INT-18916)

  • Resolved an issue where newly created components merged between branches were flagged as pending changes in later merges. Components already in sync are now shown as no change in the UI and Platform APIs. (INT-18721)

  • Resolved an issue where fields added manually to an XML profile imported from an XSD (XML Schema Definition) used the namespace of the enclosing complex type instead of the referenced element’s namespace, causing process executions to return null values. (INT-13965)

  • Resolved an issue where a selective merge deleted a process and its folder from the destination branch even when you kept the destination version during conflict resolution. (INT-17459)

    These fixes are not in the runtime release.

On this Page