Summary
The following enhancements have been made to the Customer Master Data Management solution:
- New list processing functionality allows records of a list to be processed and updated by an external service. Lists are exchanged asynchronously via hotfolders. Existing Web UI tab components can now be added for list processing, for example, to manage metadata on list processing objects. Also, list processing now includes compression of internal files as well as downloadable files to improve file transfer times and reduce disk usage.
- The 'Match and Merge' type Web Service Endpoint now gives users the option to communicate using the REST API V2, expanding the capabilities from strictly XML to a greater variety of data formats, including JSON.
- A new 'Find Similar' type Web Service Endpoint exposes Find Similar as a REST API V2 service. This service is an improvement over the existing 'getSimilarObjects' SOAP web service request, allowing a simpler and more standard way of expressing the input for the search.
- The Dun & Bradstreet (D&B) integration has been changed to the new Direct+ API, which now supports synchronous D&B matching and enrichment. Find details in the New Dun & Bradstreet Direct+ Connector release note here.
- The Customer MDM Solution Enablement section has been renamed to Customer & Supplier MDM Solution Enablement here. Content updates have been made to reflect 10.2 solutions.
Details
New list processing functionality
The list processing functionality now includes the option to process lists via external services, such as email or address validation, using hotfolder integration. A list of records imported into Web UI can be delivered to an external service using an asynchronous service configuration. When the external service returns the processed list, the asynchronous service configuration picks it up and resumes the list processing, including running a configured business action to update the record data of the list. Users can download and review the exported list and the returned list if needed.
The original Processing List Screen has been updated as a new Processing List Tab Page screen. This new screen includes the action toolbar and the process card area. Adding another tab screen allows users to manage list metadata via the existing Tab Page with Node Editor component. The List Processing Summary Card (previously part of the Processing List Screen) has been converted to a separate summary widget. This constitutes a change in functionality for customers who previously configured the Processing List Screen.
Improved list processing functionality includes file compression to conserve disk space and reduce the time to transfer files. File compression is used for internal list processing files not exposed to the user and files that can be downloaded in both Web UI and workbench.
List processing functionality is available on systems with the List Processing commercial license activated. Contact your Stibo Systems' account manager or partner manager for assistance.
For more information, refer to the List Processing topic in the Data Preparation documentation here.
Match and Merge type Web Service Endpoint allows REST API V2
The Match and Merge type Web Service Endpoint provides a synchronous alternative to the Inbound Integration Endpoint and now exposes both a SOAP service and a REST service. Expansion of the existing Web Service Endpoint object type includes a REST API V2 match-and-merge service.
Web Service Endpoint functionality is available on all systems. For more information, refer to the Web Service Endpoints topic in the Data Exchange documentation here.
Find Similar type Web Service Endpoint allows REST API V2
The Find Similar type Web Service Endpoint gives users access to the new 'find similar' entity operation. This REST service is a modernized version of the existing 'getSimilarObjects' SOAP web service request.
The 'find similar' entity operation is only available for entities and only in REST API V2. It is designed for use with a match and merge matching algorithm. 'Find Similar' can take an entity as input which enables it to properly match on data container objects and removes the need for providing the matching algorithm with a bind on every attribute required for matching.
A validation business condition can reject a search before it starts to prevent Find Similar search from finding entities in certain states. The available standardization business action can improve the matching process by normalizing or enriching the input data before running the matching algorithm.
Web Service Endpoint functionality is available on all systems. For more information, refer to the Web Service Endpoints topic in the Data Exchange documentation here.