Update 21D

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Product	Feature	Notes
10 NOV 2021	Address, Email, and Phone Verification	Verify Email and Phone Records in Bulk using Email Verification and Phone Verification API	Updated document. Delivered feature in update 21D.
10 NOV 2021	Account and Contact Enrichment	Enhanced Account Smart Data Search and Sort API	Updated document. Delivered feature in update 21D.
03 SEP 2021			Created initial document.

Overview

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.

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.

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

Feature Summary

Sales Automation Core Common

CRM Common Components

Validate Migration Sets to Check for Missing Roles in Target

You can now validate migration sets during the import process to check and report on missing roles in the target environment. Based on the validation results, you can choose to proceed with the import as-is or take corrective actions before importing.

This feature lets you check and report on missing roles in the target environment during import.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Migrate Your Configurations" topic in the Oracle Applications Cloud: Configuring and Extending Applications guide.

Enable or Disable Mass Update by Object and Specify Fields to be Updated at Once

You can specify which objects you want to enable or disable in the mass update feature in Workspace. You can also select specific fields to make available for mass update within each of the objects you enable. For example, with just a few clicks, you can select the sales stage field on the Opportunity object so that users can update the opportunity sales stage fields on multiple records at once. Or, you can enable users to update rank and deal size on several leads at once. The mass update feature improves efficiency by reducing the number of clicks when the same update needs to be done on multiple fields within objects.

These enhancements help make the mass update feature more configurable and usable.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

See this content:

• "Adaptive Search and Workspace" chapter in the Implementing Sales guide
• "Workspace" chapter in the Using Sales guide

Role Information

• Sales Administrator

Navigate to an Object-Based Workspace Page from Your Sales Springboard

Salespeople can navigate directly to a Workspace page that contains the object they selected from their Sales springboard. On the springboard, salespeople simply click a sales icon to open a Workspace page for that specific sales object.

This new navigation feature helps salespeople quickly access the fast search capabilities of Workspace and provides a superior user experience.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Sales

Key Resources

See this content:

• "Adaptive Search and Workspace" chapter in the Implementing Sales guide
• "Workspace" chapter in the Using Sales guide

Role Information

• Sales Representative
• Sales Manager
• Sales Administrator

Allow Partial Publish in Adaptive Search

You can now choose to publish a selected set of objects in Adaptive Search without building the full index. For example, you want to modify the configuration of a few already indexed objects in Adaptive Search. You can select only the modified objects to get re-indexed without rebuilding the whole index from scratch.

This feature saves processing time and helps speed up the indexing process.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Adaptive Search and Workspace" chapter in the Implementing Sales guide.

Role Information

• Administrator users with Application Implementation Consultant job role

Accounts, Contacts, and Households

Use Additional Information Related to Hierarchy and Associated Contacts in Accounts REST API

You can use Accounts REST API to get additional information about hierarchy and account contacts. The Accounts REST API is enhanced with new attributes at the accounts and account contacts levels to show additional information related to account, account hierarchy, primary contact, and other associated contacts. All added fields are read-only and non-searchable.

Accounts:

• TotalAccountsInHierarchy
• TotalChildAccounts
• ParentAccountList
• PrimaryContactEmailDNC
• PrimaryContactPhoneDNC
• PrimaryContactPhoneVerificationStatus
• PrimaryContactPhoneVerificationDate
• PrimaryContactEmailVerificationStatus
• PrimaryContactEmailVerificationDate

Account Contact child:

• DoNotCallFlag
• DoNotEmailFlag
• PhoneVerificationStatus
• PhoneVerificationDate
• EmailVerificationStatus
• EmailVerificationDate
• ContactLastUpdateDate
• ContactFirstName
• ContactLastName

Sales users can now view do-not-contact and verification status of existing contact-related information for a given account. Also, more information related to account hierarchy is available. This feature improves overall efficiency and execution.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

• See the relevant sections in the REST API for CX Sales and B2B Service.

Configure, Verify, and Build Similar Accounts Machine Learning Model Through New Admin UI

Configure, verify, and build a Similar Accounts analysis based on the Sales machine learning model using a new admin interface.

The Similar Accounts feature in Sales is a new capability that helps you customize the machine learning model to discover account similarity natively, without moving the data. You can find companies or accounts similar to an account based on preselected key attributes. The Oracle Machine Learning service available natively with your Sales instance enables the machine learning model training, testing, and deployment flow. You can enable this feature from the new administrator interface. This new interface lets you configure similar accounts by adding your own attributes to tweak the machine learning model based on salespeople's unique requirements to view similar accounts. For example, salespeople can view similar accounts by firmographics or technographic attributes, revenue, product category, or territory.

This feature helps sales administrators and sales operations staff fine tune the Similar Accounts adaptive intelligence model according to their sales organization data and processes.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Sales  No Longer Optional From: Update 23A

Use the Opt-In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Tips And Considerations

Before you opt in to this feature, you must:

1. Navigate to My Enterprise > Enterprise.
2. Click the Manage Promotion Code link.
3. Click Enter Promotion Code. To get a promo code, go to the Sales forum on Oracle Customer Connect or raise a service request on My Oracle Support.
4. Enter the promotion code for this feature. A new entry called Sales Machine Learning will be added.
5. Click Done.

After you're done the above steps, then:

1. Navigate to Setup and Maintenance by clicking the Setup and Maintenance link under your user name in the global header.
2. Select the Sales Offering.
3. Click Change Feature Opt-In.
4. For the Sales root node, click the edit icon.
5. Find the feature, Sales Machine Learning, and select the Enable check box.
6. Click Done.

Key Resources

• See the "Sales Machine Learning" chapter in the Implementing Sales guide. Note that the full documentation for this feature won't be available until the Update 22A release of Oracle Help Center.

Role Information

• Sales Administrator

Improve Quality of Account Smart Data Using DataFox

Provide a modern sales experience by leveraging smart integration with Oracle DataFox to autosuggest matching accounts and autoretrieve company details when creating accounts. This feature improves the user experience by minimizing the number of clicks and keystroke needed during account entry. It also improves data quality by retrieving up-to-date account data from Oracle DataFox in real time.

This feature means improved data quality and user experience with validated account data in Sales. 

Steps to Enable

1. In the Setup and Maintenance work area, use:
   • Offering: Sales
   • Functional Area: Integrations
   • Task: Manage DataFox Data Enrichment Integration

NOTE: If you don't find the functional area listed, refer to Configure Offerings to set it up. 

2. On the Manage DataFox Data Enrichment Integration page, enter your Oracle DataFox credentials.
3. Select Enable Smart Data for Account from DataFox and Enable Data Enrichment from DataFox.
4. Click Save and Close.

Tips And Considerations

• Enable enrichment and smart data using the same data provider, Oracle DataFox.
• Type in a few characters in the Smart Data search box to see the smart data list.

Import and Export

Export Inactive Accounts, Contacts, Households, Organizations, and Persons

You can now export inactive accounts, contacts, households, organizations, and persons using export management.

Previously, you could not export inactive or merged records, even if you explicitly included the Party Status criterion in your export filter. This enhancement addresses the need for customers (for example, Customer Data Management users) who can access inactive and merged records via REST, but can’t do the same using import/export. 

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the REST API for CX Sales and B2B Service.

Cancel Feature in Export Management

You can now cancel any long running and stalled exports in Export Management.

Users export data on a regular basis. Sometimes, due to unforeseen reasons, an export gets stuck and it's very difficult to restore the application back to its normal state. This also impacts other processes, as users might not be able to run import jobs if an export is stuck. This cancel feature adds value and saves time for customers.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

This feature was already available in Import Management, delivered in Update 21A.

Key Resources

• See the Understanding Import and Export Management for CX Sales and B2B Service guide.

Security

Access Object Records Secured Using Access Groups in Near Real-Time

You can access data that is secured using access groups in near real-time for an expanded set of objects. When an object record is created or updated, you can access the new or updated records immediately. You no longer have to run the Perform Object Sharing Rule Assignment Processing scheduled process before you get access to the records.

With this update, near real-time processing is now supported for these objects:

• Account
• Activity
• Campaign
• Contact
• Deal Registration
• MDF Budget
• MDF Claim
• MDF Request
• Partner
• Program Enrollments
• Custom objects

With this feature, users have more timely access to object records.

Steps to Enable

To implement near-real-time access to object records, enable these two profile options:

• Near Real-Time Transaction Tracking for Access Groups Enabled (ORA_ZCA_ACCESS_GROUPS_NEAR_REAL-TIME_TRACKING_ENABLED) 

  This option is enabled at the site level by default.

• Common CRM Signals Active (ORA_ZCA_ENABLE_SIGNALS). 

  This option is disabled by default. 

Enable the Common CRM Signals Active option to implement near real-time processing using these steps:

1. From Setup and Maintenance, navigate to the Manage Administrator Profile Values task. 
2. Search for the profile option name, Common CRM Signals Active. 
3. In the Profile Values section, select the Site profile level, then change the default value of the Profile Value field to Yes. 
4. Click Save and Close.

Key Resources

• See the "Access Groups" chapter in the Securing CX Sales and B2B Service guide.

Role Information

• IT Security Manager 
• Sales Administrator

Use Access Explorer to Troubleshoot a User's Access Group Permissions

Use the Access Explorer to view the data access users receive from their access group membership as well as from the roles they're assigned. You can also view the access group rules and groups that provide access to a specific object record and identify whether or not a user is assigned those rules. If users don't have the record access they require, you can drill down to a specific rule or group from the Explore page and make the necessary changes.

The Access Explorer provides an overview of a user's access to object data from access groups rules and data security policies. Using Access Explorer, you can easily identify a user's existing access and determine what you need to do to grant any additional access required. Complete, integrated support for access groups in Access Explorer lets you easily troubleshoot user access issues.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• See the "Access Groups" chapter in the Securing CX Sales and B2B Service guide.

Role Information

• IT Security Manager
• Sales Administrator

Run the Object Sharing Rules Process for Rule Changes Since the Last Update

You can run the Perform Object Sharing Rule Assignment Processing scheduled process for only those records that have changed since the process was last run.

This feature ensures access group members have up-to-date access to object records with the minimum processing time.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

When you run the Perform Object Sharing Rule Assignment Processing scheduled process, for the Record Selection parameter, select the Records Since Last Run option.

Key Resources

• See the "Access Groups" chapter in the Securing CX Sales and B2B Service guide.

Role Information

• IT Security Manager 
• Sales Administrator

Simplified Setup

Enhance Setup Assistant to Enable Adaptive Search During Onboarding

Setup Assistant can now be used to enable Adaptive Search for the objects you use in your business, so salespeople can start using Workspace right away, without additional setup.

Easily enable Workspace and Adaptive Search and ensure that certain key features, such as actionable infolets and Workspace, show data upon initial sign-on. This provides a seamless experience for customers, alleviating the need to set up Workspace after initial onboarding.

Steps to Enable

1. Launch Setup Assistant from the Sales Offering in Setup and Maintenance.
2. Follow the setup wizard to configure initial Sales setup.
3. Select the objects to be indexed as part of Adaptive Search. 
4. Submit the setup.

Tips And Considerations

• You can configure core Sales objects for Adaptive Search.
• In order to set up additional search features, launch the Configure Adaptive Search setup task. 
• Configure additional objects and do advanced setup from the Configure Adaptive Search setup task.

Key Resources

• See the "Run Setup Assistant" chapter in the Getting Started with Your Sales Implementation guide.

Customer Data Management

Data Quality

Select Customer Identifying URLs During Duplicate Identification

Ensure that only website contact point URLs that identify the customer are used for duplicate identification. You can do so by filtering non-identifying URLs out of the duplicate identification processes such as cluster key generation and candidate scoring.

This enhancement supports more extensive use of web contact points to track analytical or informational websites without reducing the effectiveness of URLs as a component of duplicate identification logic.

Steps to Enable

To use this enhancement, navigate to the Manage Standard Application Lookups setup task and create new entries under the ORA_ZCQ_FILTER_DOMAINS lookup type.

Tips And Considerations

The Duplicate Identification process evaluates the domain name portion of URLs to help determine whether a set of customer records are likely to be duplicates of each other. This feature helps ensure that distinct customer records aren't incorrectly classified as duplicates as a result of having a common domain name present in the web contact points collection when that domain name doesn't actually identify the organization. For example, customer records can be given web contact points based on social websites, analyst websites, or other types of web resources that use a common domain name when referencing the customer in a query string or page-level locator. By registering those common domain names, the duplicate identification process doesn't consider those web contact points.

Key Resources

• See the "Duplicate Identification Setup" chapter in the Implementing Customer Data Management guide.

Role Information

All setup users with access to Manage Standard Lookups can configure this feature.

Address, Email, and Phone Verification

Use Organization and Person REST Resources to Access Contact Point Validation Status

Use Organization and Person REST API resources to access contact point validation status and find out whether phone numbers and email address contact points have been validated.

This enhancement allows phone and email address validation status to be understood by integrated Spoke systems within an applications ecosystem.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

This enhancement adds new elements to the data structure of the hubOrganizations and hubPersons REST resources. There are no other changes to the functionality and usage of these APIs.

Key Resources

• See the relevant sections in the REST API for CX Sales and B2B Service guide.

Role Information

All roles that can currently access the hubOrganizations and hubPersons REST resources can use this enhancement.

Verify Email and Phone Records in Bulk using Email Verification and Phone Verification API

Verify email and phone records in bulk using the email verification and phone verification API. The API is specifically for verifying large number of records. You can use the API to batch verify email and phone records.

Customers can verify larger number of email and phone records in a single API call, instead of verifying records one by one. This approach helps in efficiently verifying large numbers of phone and email records, and then importing the results into CX Sales using Import and Export Management.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

In a single REST API call, users can verify up to 200 phone or email records using the API. The API can be invoked multiple times to verify larger number of records.

Key Resources

• POST operation support has been added in the existing REST API resources /av/api/v3/email/verify and /av/api/v3/phone/verify for processing larger numbers of records. For detailed information, see Phone Verify and Email Verify in REST API for Oracle Address, Email, and Phone Verification.

Customer Hub

Adopt Latest Industry Guidelines for Customer Data Management Terminology

Replace references to merge survivor records with the term master records, and replace references to merge victim records with the term non-master records to more accurately convey the meaning of merges.

In particular, the Data Quality Rules module for configuring merge logic with Groovy script has been updated to provide new internal functions called getMaster() and getNonMasters() to instantiate row objects for the master and non-master parties within the merge scope. These function calls replace the previous getSurvivor() and getVictims() terminology.

This enhancement standardizes our documentation and API names with clear and concise terminology.

Steps to Enable

The documentation, message, and API names are available for use.

Tips And Considerations

Any existing Data Quality Rules scripts that use previous terminology will continue to work; however, any new script development should use the updated API names to reference the master and non-master parties within the merge scope.

Key Resources

• See the "Set Up Duplicate Resolution Using Groovy Scripts" section in the Implementing Customer Data Management guide.

Role Information

Users with the Master Data Management Application Administrator role can manage all Customer Data Management setups, including the use of Application Composer to configure data quality rules.

Use Import Management to Update Source System Reference Values

Use Import Management to update existing source system reference values. You must use the hubSourceSystemReferences import object to update active source system reference records.

This enhancement provides a simplified transaction model for correcting erroneous source system reference values with a direct update, instead of requiring an effective-dated update.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Include the Source System Reference ID value in the CSV row to directly update the Source System Reference Value attribute.

Key Resources

• See to the "hubSourceSystemReferences" section in the Understanding Import and Export Management for CX Sales and B2B Service guide.

Role Information

All roles that can access the hubSourceSystemReferences REST resource can use this enhancement.

Use REST API to Update Source System Reference Values

Update the source system reference values on active source system reference records through the hubSourceSystemReferences REST resource. You can now use the PATCH method on the hubSourceSystemReferences resource to directly modify the source system reference value attribute.

This enhancement provides a simplified transaction model for correcting erroneous source system reference values with a direct update instead of requiring an effective-dated update.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

Use the standard REST PATCH operation by using the SourceSystemReferenceId in the resource locator.

Key Resources

• See the "hubSourceSystemReferences" section in the REST API for CX Sales and B2B Service guide.

Role Information

All roles that can access the hubSourceSystemReferences REST resource can use this enhancement.

Account and Contact Enrichment

Enhanced Account Smart Data Search and Sort API

The Company Find API has been enhanced to provide better results for typeahead-style search. The API now gives higher relevance to records that match company name or trade style name and also sorts them based on a score assigned to revenue and number of employees.

The suggested company list rendered by Account Smart Data in CX Sales does not always render the company the user is looking for within the top 5 records. This is because the current Find API used by Smart Data searches across a predefined set of fields in sequential order starting with Company Name first, followed by Trade Style Name, Street Address 1, Street Address 2, City, State Name/Province, State Abbreviation, Zip Code, and Country respectively. In addition, the API returns records where the text is found in any of the searched fields, and sorted randomly. This leads to user confusion. With the introduction of this enhancement, Account Smart Data gives higher relevance to records that match the Company Name or Trade Style Name and sorts them based on a score assigned to Revenue, Number of Employees, and Company Type.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• REST API /token/api/v4/company/find. More information can be found at https://docs.oracle.com/en/cloud/saas/social-data-insight-cloud/rrdat/op-token-api-v4-company-find-get.html

IMPORTANT Actions and Considerations

IMPACT OF SAFARI 14 SECURITY AND PRIVACY CHANGES ON MASHUPS EMBEDDED INTO FUSION APPLICATIONS

Apple Safari 14 introduced new security and privacy changes that block third-party cookies. As a result, if you embed into Fusion Applications any mashup that requires a third-party (non-Oracle) identity provider, then the mashup doesn’t load at runtime in Safari 14. Users can avoid this issue by using Google Chrome or Mozilla Firefox, although other browsers could introduce similar changes in the future. Safari users can also optionally disable the “Prevent cross-site tracking” privacy setting as a workaround.

------------------------------------------------------------

POST-UPDATE TASKS

UPDATE APPLICATION COMPOSER CUSTOMIZATION TO THE LATEST ENHANCED BEHAVIOR

During your upgrade, most existing customizations made in Application Composer are automatically updated to the latest enhanced behavior in the new release. However, there are a few exceptions that require you to manually initiate the upgrade script for each of those customizations.

NOTE: Some upgrade tasks will not be removed from this page even after the upgrade is completed, as they are re-runnable for certain feature enhancements that are expected in future releases.

STEPS TO ENABLE

You must sign in as a user with an administrator role to perform these steps.

IMPORTANT: Do not perform these steps when there are pending changes in an active sandbox. Be sure to save and publish sandboxes with any changes you want to keep before proceeding, and delete any sandboxes that you do not intend to publish.

1. Sign into the application.
2. From the Navigator, select Sandboxes (under Configuration).
3. Create a new sandbox and set it as the active sandbox. The current active sandbox displays at the top of the application.
4. Go to: Navigator > Application Composer (under Configuration).
5. From the Application drop-down list, select the first application whose metadata you want to upgrade, such as Common or Sales.
6. From the navigation tree on the left, under Common Setup, click Metadata Manager.

NOTE: You need to upgrade the existing customization metadata for each application separately.

7. Click Metadata Upgrade.
8. By default, the list displays the Not Started upgrade items that you need to manually upgrade. Highlight the first row in the list, and then click the Upgrade button.
9. Click OK in the confirmation dialog box. This process may take a couple of minutes. When the upgrade is done, the dialog box closes and the Upgrade Completed column shows an indicator.
10. Repeat steps 7-8 for each row in the list.
11. Repeat steps 4-8 for each application in the Application drop-down list in Application Composer.
12. Publish the sandbox.

After the processes have completed, the application is ready to use.

KEY RESOURCES

• Read Prepare for Your Quarterly Update (Doc ID 2445338.1) on My Oracle Support to learn how to prepare for and validate your quarterly update.