Here are some of the highlights of the October 2016 release. For the complete list, see:
- Goodies for Process Developers
- Platform Administration
- Master Data Management
Goodies for Process Developers
Drag-and-Drop from Component Explorer
This one's pretty cool. Choosing components is a very common task when building processes. The type-ahead search added to most choosers is great but now you have another option.
You can drag components directly from the Component Explorer onto the process canvas, process shape, or component configuration dialog. Want to quickly create a map shape? Just drag and drop the profiles and even a map function. This is super convenient when you have the component explorer open to where all the components for a given process are and especially if you've organized with a lot of folders.
Now keep in mind not all components make sense to drop in all situations (what would dropping a Profile on the process canvas mean?). The highlighted drop zone lets you know what's possible. Also some component dialogs don't yet support this capability but we're working on those.
Copy and Paste Map Functions
Another crowd-pleaser to be sure. Quickly duplicate that complex connector call or custom scripting function you just configured within the same map or even across maps. Similarly you can copy function steps within user defined map functions. Upon copying you'll get a banner at the bottom of the screen letting you know there's something on the clipboard that can be pasted.
(See video above)
Cross Reference Table Lookups Gone Wild
Wildcards that is. Many cross reference lookups are straightforward, exact match use cases (think State Abbreviation >> State Name). But sometimes you might have many similar input values that should all give the same result. Previously you would've had to populate the table with every possible combination. Not the best way to spend the afternoon (although you would probably just whip something up in Excel and import from CSV but you get the point).
Suppose you had 100's of employee job codes that happened to include the region identifier (e.g. USA123, CAN456, IND789) and your objective was to get the region name (e.g. United States, Canada, India). Instead of adding every single job code to the table, you can use wildcards like this:
Done! You can also use Regular Expression syntax for even more sophisticated pattern matching.
A few things to keep in mind:
- The intent of a cross reference table lookup is still to return a single row.
- The lookup stops at the first match which means the sequence of the rows becomes more important now that it's possible to use wildcards with varying specificity. In other words, be sure to put the most specific matches first.
- Tip: To help with ordering the rows, consider adding a column for "Rank". Enter the numeric ranking and simply click the column header to sort by that column.
Trading Partner API
When migrating from another EDI solution to AtomSphere, you need to bring over all the trading partner definitions including standard control and communication information, which can mean a lot of typing and clicking if you have dozens let alone hundreds of trading partners.
With the new Trading Partner API you can programmatically generate much of the trading partner component configuration. Assuming you can extract the details from your previous application into a structured format (CSV, XML, DB, or anything else that AtomSphere can map), you can a build a simple process using the AtomSphere API connector to create the trading partner components for you.
- Not everything can be set such as document types. Regardless your fingers and mouse button will thank you.
- Only the Create action is supported at this time.
Release Control Scheduling for Everyone
Applying release control to your Atoms is now even easier. Set a release control schedule ahead of time to always apply pending updates automatically when you want without having to A) remember to do it or B) wake up in the middle of the night to click the button.
For more on understanding platform updates and release control, check out Boomi Product Release Cadence and Flexibility.
In-App Banner Prior to Platform Restart
To help with visibility into the release status, a new message is displayed right in the application warning you to save your work because the platform's about to restart!
A few additional things to help protect you and your data...
- Logout of ALL active sessions across devices.
- Define a user session timeout policy for your account.
- Improved password-reset notifications including by who and when it was requested.
- Amazon S3
- Automatically pages results when >1000 files returned
- Optionally set server-side encryption when reading and writing (Customer Idea!)
- HTTP Client
- Ability to set the HTTP connection and read timeout for an individual connection. This overrides the default timeouts set in the Atom runtime's vmoptions (2 minutes) allowing you to aggressively terminate or patiently wait for connections at your discretion.
- Added support for the "realm" parameter used for some implementations of OAuth 1.0.
- Support added for OAuth Client Credentials and Resource Owner Password Credentials authentication flows.
Master Data Management
Source Governance Rules
If you have some application sources that shouldn't be allowed to "touch" certain golden record fields, you can define governance rules to exclude the values for specific fields contributed by certain sources. For example, perhaps the sales/CRM application shouldn't be allowed to modify the Payment Terms field "owned" by the finance application. This is important because it puts the control in the hands of the MDM Administrators vs. the individual integrations sending records to MDM.
Outbound Delivery Rules
Similarly on the outbound side, perhaps some applications don't care about updates to certain records. Now you can define delivery rules based on golden record tags for all types of outbound messages including Update and Delete (previously this was only available for Create messages). This avoids unnecessary messages flying around.
Manage all those fine-grained entitlement permissions for data stewardship access at the role level to easily grant similar access to multiple users. Previously this was only available at the individual user level (note you can still set entitlements at the user level for specific exceptions). The entitlement configuration options are the same.
Tip: Take advantage of custom role inheritance to manage different levels of access across data stewards.