Runtime Release Notes for May 2025
- Release notifications in stats.boomi.com and the Runtime and Platform release topics will now contain information regarding runtime Java updates and their schedules. (RUN-8890)
- Improved runtime release services to ensure runtime updates are applied efficiently and reliably. (RUN-8629)
- As a convenience to end users in troubleshooting and API development, we added a Copy button for Environment ID to easily copy the value to the user’s system clipboard. (RUN-8560)
- Renamed the Cloud Management privilege to Private Cloud Management to better distinguish between private clouds and dedicated clouds. There is no change in the functionality of this privilege. (RUN-8816)
- Atom Queue Connector, the number of Executions spawned by the Listener is now Limited to the Maximum Concurrent Executions per Listener Account Quota when set. When a Connector operation has unlimited executions, it is limited by the Maximum Concurrent Executions Per Listener. (RUN-8873)
- Dedicated Cloud service enhancements
- Dedicated Clouds can now be reset after initial configuration. Resetting a dedicated cloud deconstructs the cloud infrastructure and allows customers to reconfigure any configurable aspect of the cloud.
- This should be done carefully, as it requires deleting all of the cloud attachments and will remove all execution history.
- This does not allow users to change cloud classification, region, DR region, or Cloud Option.
- Dedicated Cloud DNS Address was changed to a FQDN (RUN-8711)
- Dedicated Clouds workflow improved when being configured from multiple screens.
(RUN-8494)
- Dedicated Clouds can now be reset after initial configuration. Resetting a dedicated cloud deconstructs the cloud infrastructure and allows customers to reconfigure any configurable aspect of the cloud.
- Privilege Improvements
-
Users with the Runtime Management Read Access and Scheduling privileges can now update the process schedule through the UI. (RUN-8316)
-
Users with the Runtime Management Read Access and Execute privileges can now run the process through the UI. (RUN-8315)
-
A new Persisted Process Property Read and Write Access privilege has been added, which enables users with Runtime Management Read Access to edit the Persisted Process Properties. (RUN-8274)
All of these new privileges are accessible under Settings > Account Access > User Management in UI.
-
Users with Persisted Process Property Read and Write Access privilege and Runtime Management Read Access privilege can now update the Persisted Process Properties through PersistedProcessProperties API. (RUN-8354)
noteThe Persisted Process Property Read and Write Access privilege works with Environment Management Read Access and Environment Management Full Access privileges. To ensure this works, you must also have either Runtime Management or Runtime Management Read Access privilege.
Privilege Description Administrator Role Standard User Role Production Support Role Support Role Persisted Process Property Read and Write Access You can view and edit the persisted process properties. Included Included Included Excluded
-
- Restarts are no longer required after deploying scripting custom library components. (RUN-8160)
- The Runtime Information screen now correctly displays the install date for when a cloud attachment was created rather than the date of the associated cloud. (RUN-8611)
- Atom queue executions no longer block server shutdown. (RUN-7851)
- For Linux only: The procworker, procrunner, procbrowser, and Atom start script files (.sh and .ps1) now log JVM startup entries, including when it fails to start, to the runner.log file. JVM startup failure logging is enabled by default via the custom container property
com.boomi.container.enableRunnerLogIfJVMFails. (RUN-2994) - The Clear Queue API no longer requires passing an additional field
idto AtomSphere and Partner AtomSphere Connectors. (RUN-7377) - Improved the error message to provide clarity for process execution failure. (RUN-8888)