Master Data Hub release notes for 14 Sep 2019
The following list shows new features, enhancements, and bug fixes in the Master Data Hub September 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.
|Platform||HUB-342||Previously you could only partially configure a source when you attached it to a domain. Now you can fully configure sources when attaching them.|
To learn more about this new feature, see the topic Attaching a source to a domain.
|Platform, Repository||HUB-345||Previously you could not rank field groups when you configured source rankings. Now you can rank field groups. If a golden record update changes the value of a field in a ranked field group, the contributing source is considered, going forward, to be the contributing source for the field group.|
To learn more about this new feature, see these topics:
|Platform, Repository||HUB-415||Previously you could not selectively merge reference fields when you resolved matching issues for quarantined entities. Now the Resolve Matching Issues wizard lets you select reference fields for merging.|
To learn more about this new feature, see the topic Resolve Matching Issues wizard.
|Platform||HUB-344||It is now easier to apply filtering by source in Outbound Reporting. Extra clicking was previously necessary.|
|Repository||HUB-308||When a Boomi Integration process call data quality step is executed on an incoming source entity, the source entity ID and golden record ID are now passed as dynamic document properties to the MDM Listener connector.|
To learn more about this enhancement, see the topic Boomi Integration MDM listener process building.
|Repository||HUB-419||You may notice improved performance as a result of a new limit on the number of source record update requests evaluated for possible delivery in a single batch on a source’s channel.|
To learn more about this enhancement, see the topic Fetch Channel Updates.
|Repository||HUB-196||Upon restoring a referenced end-dated golden record, the references remain unresolved.|
|Repository||HUB-245||An error occurs in certain cases when attempting to approve a quarantined entity after a new version of the model is deployed.|
|Repository||HUB-326||When a golden record is updated as a result of a data quality step, tag-based restrictions on the propagation of source record update request to the contributing source are disregarded.|
|Repository||HUB-347||An error occurs during the processing of an incoming entity that contains an empty collection field in a non-repeating field group.|
|Repository||HUB-360||A Boomi Integration MDM listener process is erroneously called from a data quality step during the processing of an incoming entity in which a reference field value is unchanged from the field value in the corresponding golden record.|
|Repository||HUB-373||Requests for pending deliveries of source record update requests on a channel are blocked while a pending delivery exists for an update to a purged golden record.|
|Repository||HUB-413||In certain cases updates are erroneously listed in golden record history for incoming entities in which data was unchanged.|
|Repository||HUB-435||In certain cases filtering golden records by a collection field value returns duplicate results.|
|Repository||HUB-450||A data quality step may not be performed on an incoming entity if that entity is in multiple batches undergoing simultaneous enrichment.|
|Repository||HUB-471||An error occurs in some cases when a source for which tag-based delivery is configured contributes an entity that is a duplicate of a golden record that was contributed from another source and enriched during incoming processing. With this fix, an error does not occur under the same conditions. This fix required a re-release of the Repository to Hub clouds.|
|Repository||HUB-472||An error occurs when an incoming entity is sent to Loqate for enrichment. With this fix, entities in a batch are sent to Loqate for enrichment as expected. This fix required a re-release of the Repository to Hub clouds.|
|Repository||HUB-476||A Clear Model Data operation does not complete if the operation’s Also reset sources to Created (pre-Initial Load) state option is selected. With this fix, Clear Model Data operations should complete regardless of whether the option to reset sources is selected. This fix required a re-release of the Repository to Hub clouds.|