Master Data Hub release notes for 13 Jul 2019
The following list shows new features, enhancements, and bug fixes in the Master Data Hub July 2019 release
Subject to the terms and conditions of our existing contract with your firm, and liability provisions and limits therein, we confirm that Boomi has successfully passed all applicable test cases associated with the updates identified in this product release.
Release notes for the 12 months preceding the current release are archived.
Issue summary
| New features | ||
| Area | ID | Summary |
| Platform, Repository | HUB-174 | Add the capability to end-date filtered golden records in bulk either in the Golden Records page or programmatically.For more information, see: |
| Platform, Repository | HUB-179 | Add to the Golden Records page the capability to perform the following actions:
For more information, see Purging end-dated golden records. |
| Platform, Repository | HUB-233 | Add to the Historical Reporting page the capability to request counts of requests to MDM listener processes from Boomi Integration process call data quality steps applied to incoming source entities. For more information, see Historical Reporting page. |
| Enhancements | ||
| Area | ID | Summary |
| Platform | HUB-296 | Optimize the loading of the Dashboard, Outbound Reporting, Golden Records, Quarantine, and Staged Entities pages. |
| Repository | HUB-278 | Add the option to the Query Golden Record operation in the repository API to request the inclusion of source links in the results. For more information, see Query Golden Records. |
| Repository | HUB-281 | Add support to the Query Golden Record operation in the repository API for querying by one or more golden record IDs. For more information, see Query Golden Records. |
| MDM connector | HUB-243 | Add the capability to fetch source record update requests on a channel one at a time. For more information, see MDM operation’s inbound actions. |
| Fixes | ||
| Area | ID | Summary |
| Platform | HUB-288 | An incorporation error occurs when applying a match rule that matches either an incoming collection field to a different existing collection field or a non-repeatable field to a collection field. With this release, it is no longer possible to create a match rule for collection field matching in which an incoming collection field is not matched to the corresponding existing collection field. |
| Platform | HUB-298 | An error occurs in the Golden Records page while the data grid is filtered by field data upon selection of a different domain. |
| Repository | HUB-346 | An error occurs when attempting to end-date golden records in a domain that has an attached source to which source record update requests are sent based on the presence of certain golden record tags. |
| Repository | HUB-359 | Multiple updates to the same golden record are not coalesced into a single source record update request as was the case before the June 2019 release. With this release, the previous coalescing behavior is restored. |