Skip to main content
Feedback

Integration Release Notes for March 2025

Platform Release

March 8 2025
Important

In the March 2025 Platform release, Boomi will update some of the terminology for our services. This is to make Boomi-specific terms more intuitive, better align with common industry concepts, and provide more specificity as our platform evolves. (INT-13400)

To learn more, refer to Boomi terminology changes.

The following table lists the terms that will get updated in the platform release:

Old termNew termJira ticket number
Boomi AtomSphere Platform, Boomi AtomSphere, AtomSphereBoomi Enterprise Platform, Boomi PlatformINT-13695
Atom, Containerruntime (generic)INT-14127
Atombasic runtime (specific)INT-13699
Moleculeruntime clusterINT-14128
Atom Cloudruntime cloudINT-14130
Cloud Moleculeruntime cloud clusterINT-14129
Cloud Atomcloud attachmentINT-14131
Boomi Cloud, Public Atom Cloud, Public Cloudpublic runtime cloudINT-14132
Private Atom Cloud, Virtual Private Cloudprivate runtime cloudINT-14133
Atom ManagementRuntime ManagementINT-14134
Atom Workerexecution worker (specific)INT-14136
Atom Workerruntime worker (generic)INT-14137
ShapeStepINT-14135
New
We added these features

  • Added new APIs and updated the AccountGroup object to manage the Publisher Integration Packs programmatically.

  • Added the following privilege for Branch and Merge access:

    PrivilegeDescriptionAdministrator RoleStandard User RoleProduction Support RoleSupport Role
    Branch Read and Write AccessRead access to processes and components on all branches. Write and modify permissions on all branches except main.ExcludedExcludedExcludedExcluded

    (INT-13425, INT-13892, INT-13652, INT-13651, INT-13628)

    To learn more about this feature, refer to User roles and privileges and Parallel development with Branch and Merge.

  • If you have the Branch Read and Write Access privilege, you can use the Component object and Component Metadata object with any branch excluding main and the Component Reference object with any branch including main. (INT-13650, INT-13629, INT-13453)

    To learn more about this feature, refer to Component object and Component Metadata object.

Fix
We fixed these issues

  • Adding a new element to the flat file profile in data map extensions now returns the expected results while using a multi-attach integration pack in a process. (INT-12452)

  • The extended fields of the newly added components are now listed on the Extensions page when applying a pending version of an updated multi-attach integration pack to a sub-account before the scheduled release date. (INT-10205)

  • New fields added to a profile are now accessible from the Business, Decision, and Set Properties steps. (INT-14314)

  • Improved Build page load performance by preventing multiple injections of the same JavaScript file. (INT-14260)

  • When you attempt to merge with unresolved conflicts, the Merge Request object returns a 400 error with a descriptive message. (INT-13885)

  • The Merge Request object validates the user's privileges and checks for an existing merge between branches, providing a more descriptive error message if one already exists. (INT-13866)

  • Extended properties properly show in the Extensions tab while running a process in test mode when Branch & Merge is enabled. (INT-14439)

  • When you install a process from the Process Library, it installs correctly on the current branch. (INT-13816)

  • When you merge the main branch into another branch, components that were deleted in the main branch properly show in the Merge Review wizard. (INT-14381)

  • When running a process in test mode, extensions are branch-aware, so that available extensions depend on the current branch. (INT-14430)