New Features Released for Dell Boomi Platform
We thought we’d post some of the recent changes and new functionality added to the Del Boomi Platform. Some of these are additional features to the API Stack while others are new functionality in existing shapes (as in the try/catch shape) and the New proxy settings for Atom, HTTP, SOCKS4, and SOCKS5 protocols provide the ability to add a userID and password to key-based authentications. Overall some really really cool stuff and we hope that you will find them useful in your project or implementation!!!!!!
Please read on and see if one of these enhancements or new features will work for you!
What’s New in Boomi AtomSphere:
Dell has added the following improvements to the July 2015 release of Dell Boomi AtomSphere. For more information, please see the July Release Notes in the AtomSphere Reference Guide.
Atom Message Queuing
The performance of Atom message queues has been improved. In Windows NTFS file systems you should see a performance improvement of up to 60%. In Linux Ext4 file systems you should see a performance improvement of up to 160%.
The following operations can now be requested programmatically via API calls:
• Cancel a process execution (Partner API only)
• Access process logs
When you are using the API to update the Atom Extensions, Environment Extensions or Widget Instance Extensions objects, if you are not specifically updating passwords you no longer have to provide the password values as extensions. In other words, if you are not updating the passwords you would send the Password element but not its value. For details see the Object UPDATE Operation section of the Atom Extensions, Environment Extensions or Widget Instance Extensions topics.
You can use the API to perform create, update, and execute (browse) functions on flat file profiles in Atom and environment data map extensions.
Atom Purge Process
Atoms no longer run a purge process immediately after they restart. Instead, purging occurs at the Atom’s next scheduled purge interval. If an Atom starts or restarts at the time at which its purge process is scheduled to run, the purge process will not run until its next purge interval. Purging can occur only when the Atom is online and communicating with the platform.
Schema and table filters were added to the profile’s Database Import Wizard to limit the number and speed up returned tables.
The Try/Catch shape has been enhanced to allow you to catch process errors as well as document errors. If you would like an instance of the Try/Catch shape to catch both types of errors, set its Failure Trigger field to All Errors. By default this field is set to Document Errors, which means that only document-level error are caught. Try/Catch shapes in your existing processes are set to catch only document errors.
If a process contains one Try/Catch shape followed immediately by a second Try/Catch shape, the first Try/Catch shape will catch document and process errors, regardless of how its FailureTrigger is set. The second Try/Catch shape will catch errors as indicated by its Failure Trigger setting.
On the Process Reporting page when you filter by “Errors” the list of processes that have executed, you now see all executions with document OR process errors.
Atom, AS2, MLLP and Shared Web Server logs and artifacts are available from the current date back to the latest purge date. You can attempt to download logs or artifacts from a date outside this range. If you do so, a warning message appears. You can change the date or keep it. In some cases you may need to select a date outside the range. For example, you and your Atom could be located in different time zones. If processes ran early on Thursday morning, but where you are located it is still late Wednesday evening, you could legitimately need to download “tomorrow’s” logs today. If no logs are available for the selected date, a message appears.
• After you have created a process and saved it, you need to deploy it. Now there is a quick and easy way to navigate to the process on the Deploy page. Click the View Deployment button on the process. The process closes on the Build page, focus switches to the Deploy page, and the process appears in the Processes list. Now you can attach and/or deploy the process. The View Deployment button is available only if you have saved your changes to the process and you have access to the Deploy page.
• The View Deployment button also appears on web service components on the Build page, allowing you to navigate to them quickly on the Deploy page.
• When you click Execute Process on the Process Reporting page, the list from which you select an Atom now displays the Atoms in alphabetical order by name.
• When a single-install integration pack is renamed, the accounts with which it’s shared will see its new name.
• In top-down dialogs, pressing the Esc key closes the dialog. In Process Reporting, pressing the Esc key closes the most recently opened sliding details view.
• The default value for the Folder drop-down menu is whatever you previously chose for your folder destination.
• In information messages, the focus is set to be OK/Cancel buttons to allow for keyboard navigation and selection.
• The Revision History window always opens as the top-most window displayed.
New proxy settings for Atom, HTTP, SOCKS4, and SOCKS5 protocols provide the ability to add a userID and password to key-based authentications.
We hope these improvements will assist you in optimizing your use of AtomSphere and Dell Boomi. If you have any questions or comments, please contact me at firstname.lastname@example.org