This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Feature | Notes |
|---|---|---|
| 20 MAR 2020 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.
Column Definitions:
Features Delivered Enabled
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Action is Needed BEFORE Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
Use a New Setup and Maintenance Task to Separately Configure Oracle Address Verification |
||||||
Provide the ability to control when merge notifications are sent. You can enable or disable notifications at the individual resolution request level and at the duplicate identification batch level. You can also disable notifications altogether. You can now configure the default notification status for manually created resolution requests.
When you create a duplicate identification batch, you can specify whether the application sends notifications for the resulting merge requests.
Notification Parameters in the Duplicate Identification Batch Job Definition
On the Duplicate Resolution page, data stewards can toggle the notification parameter for individual resolution requests by using the new Notify action.
Notifications Indicator and Notify Action on the Duplicate Resolution Page
In the Manage Customer Data Management Options setup task, you can define the default notification parameter value for new merge requests or disable merge notifications altogether.
Merge Request Notifications Setup
Steps to Enable
To control the default value for the merge notification parameter or to globally disable merge notifications, set the Merge Requests Notifications option in the Manage Customer Data Management Options setup task in Setup and Maintenance.
Tips And Considerations
To get the most value from this enhancement, keep the following in mind:
- The delivery of this enhancement doesn't change merge notification behavior unless you choose to make those changes.
- If you have pending merge requests created before receiving this enhancement, their merge notification parameter value is set to Yes. If you don't want to receive notifications for these merge requests, you can:
- Change the value of those pending requests to No by navigating to the Duplicate Resolution page, selecting the requests, and then choosing the Notify action from the action menu.
- Globally disable merge notifications by using the Manage Customer Data Management Options setup task to set the Merge Notifications option to 'disable merge process notifications' while the requests are being processed.
- Save time by only generating merge notifications when you want them.
Key Resources
See the Implementing Customer Data Management guide available in the Sales area on the Oracle Help Center.
Role Information
Customer Data Steward, Data Steward Manager, and Master Data Management Application Administrator roles can enable or disable merge notifications in the Duplicate Identification and Duplicate Resolution flows. The Master Data Management Application Administrator role can also configure the merge notifications feature with the Manage Customer Data Management Options setup task.
Use Groovy Script to Configure Merge Survivorship Rules
Create Groovy-script-based survivorship rules in Application Composer to configure how master records are chosen, how the master record's attributes are derived from the duplicate parties, and special conditions when merges should not be allowed. Groovy is an easy, powerful, flexible, standards-based scripting language that you can use to extend processing logic throughout the application. In this release, we provide the option to also use Groovy to write data quality survivorship rules. This option lets you standardize on a single-logic extension platform and take advantage of Application Composer's Groovy scripting interface and sandbox-enabled development process.
Data Quality Rules Task in Application Composer
Steps to Enable
This feature is enabled by launching the Manage Customer Data Management Options setup task and then selecting the Groovy script options for the Master Record Selection, Agreement Rules Type, and Add Groovy to Attribute Selection setup options. You can also use the Data Quality Rules task in Application Composer to write the Groovy scripts.
Tips And Considerations
Enablement:
- Any survivorship rules written through the Manage Survivorship Rules setup task, which use the Oracle Business Rules framework, continue to function if you don't enable Groovy script survivorship rules.
- For a given survivorship process type, such as Set Master or Agreement Rules, you can either use Groovy script or Oracle Business Rules. You can't combine the two frameworks for a single process type.
- You can combine Oracle Business Rules and Groovy script between different survivorship process types, such as using Oracle Business Rules for Set Master logic and Groovy script for Set Attribute logic.
Testing and deployment:
- Groovy script survivorship rules are developed in Application Composer using a sandbox and they can be tested in the sandbox by using the Create Resolution Request task and selecting the Test Merge resolution request type.
- The sandbox with Groovy script survivorship rules must be published before the rules can be used by the Request Dispatch process.
- Sandbox publication overwrites previously published Groovy script survivorship rules with the script content of the newly published sandbox.
Best practices for performance:
- Try to use attribute source confidence as much as possible for your Set Attribute survivorship logic.
- Select one of the 'use source confidence' Attribute Selection Type options from the Manage Customer Data Management Options setup page.
- If needed, use Groovy script along with your source confidence configuration to handle exception scenarios.
- Use survivorship Groovy scripts for survivorship logic, not as a generalized scripting event point.
- Keep your survivorship scripts fast and lean.
- Focus on using the in-context Resolution Request object to achieve the specific Set Master, Set Attribute, and Agreement Rules logic needed for correct merge processing.
Key Resources
These resources can help you get the most value from this feature:
- Oracle Applications Cloud Groovy Scripting Reference, available in the Sales area on Oracle Help Center
- The 'scripting' section of the article, Performance Best Practices for Extending Oracle CX Sales and B2B Service (Doc ID 2170121.1), available on My Oracle Support.
Role Information
The Master Data Management Application Administrator role can enable this feature and write data quality Groovy scripts in Application Composer.
Use a New Setup and Maintenance Task to Separately Configure Oracle Address Verification
Use a new Setup and Maintenance task titled Manage Integration with Oracle Address Verification to configure Oracle Address Verification. You can navigate to this task from the Integrations functional area from the Sales offerings. Alternatively, you can search for this task in the Setup and Maintenance work area in the Search available from the Tasks panel tab. Previously, a single setup task was available to configure both Oracle Address Verification and Oracle Data as a Service (Oracle DaaS) data enrichment from Dun & Bradstreet Corporation (D&B). Now you can configure data enrichment separately, using either Oracle DataFox or D&B as the data source.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
If you are a DataFox customer, you can now configure Address Verification using this new Setup and Maintenance task. If you are an existing customers using the Manage Oracle Engagement Cloud to Oracle Social Data and Insight Cloud Service Integration Setup and Maintenance task to configure DaaS for Sales and Address Verification, there is no impact on your implementation. However, it is recommended that you reconfigure Address Verification using this new Setup and Maintenance task.
Key Resources
See these guides on Oracle Help Center:
- For implementation with CX Sales and B2B Service:
- Oracle CX Implementing Customer Data Management for CX Sales and B2B Service
- Oracle CX Sales Getting Started with Your Sales Implementation
- For Customer Data Management implementation with other cloud services, such as B2C Service:
- Oracle CX Getting Started with Your Customer Data Management Implementation
- Oracle CX Implementing Customer Data Management
Role Information
- Sales Administrator
- Master Data Management Application Administrator