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
29 NOV 2021	Intelligent Advisor	Compare and Merge Project Versions	Updated document. Delivered feature in update 21D.
17 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.

Update Tasks

This section gives you information to help you plan, deploy, and validate your update. We make frequent additions to this document, so don’t forget to check back and get the latest information before your update starts.

Use the following resources to prepare for, deploy, and validate your update:

• 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.

• Publish or delete any in-progress sandboxes. Read the Overview of Sandboxes topic in the Configuring and Extending Applications guide for more information.

• Review the latest Known Issues and Update Documents for this release (Doc ID 1603154.1) on My Oracle Support.

• Review Oracle CX Sales and B2B Service: Removed Features (Doc ID 2530879.1) on My Oracle Support.

• Review the IMPORTANT Actions and Considerations in this document, to see what additional actions you may need to take after your update.

Optional Uptake of New Features (Opt In)

Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business. Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users by stepping through the following instructions using the following privileges:

• Review Applications Offering (ASM_REVIEW_APPLICATIONS_OFFERINGS_PRIV)
• Configure Oracle Fusion Applications Offering (ASM_CONFIGURE_OFFERING_PRIV)

Here’s how you opt in to new features:

1. Click Navigator > My Enterprise > New Features.
2. On the Features Overview page, select your offering to review new features specific to it. Or, you can leave the default selection All Enabled Offerings to review new features for all offerings.
3. On the New Features tab, review the new features and check the opt-in status of the feature in the Enabled column. If a feature has already been enabled, you will see a check mark. Otherwise, you will see an icon to enable the feature.
4. Click the icon in the Enabled column and complete the steps to enable the feature.

For more information and detailed instructions on opting in to new features for your offering, see Offering Configuration.

OPT IN EXPIRATION

Occasionally, features delivered Disabled via Opt In may be enabled automatically in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially automatically enabling the feature. You can also click here to see features with Opt In Expirations across all Oracle Cloud Applications.

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.

Sales Automation Foundation Common

Leads and Opportunities

View Recommended Contacts for Leads and Opportunity to Optimize Deal Execution and Lead Nurturing

You can improve your sales effectiveness and gain productivity by receiving key data insights on contacts for leads and opportunities. Using data analytics and mining, Sales Insights recommends key contacts for each active opportunity or lead for the relevant account to help effectively close the deal.

Contact recommendations are based on historical data, contacts relationships, and the successful interactions associated with an opportunity or a lead.

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 22C

Contacts Recommendations is a new feature under the Sales Insights feature set released in Update 21B. The steps to enable are the same as those provided in the Implementing Sales guide for Sales Insights.

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

Key Resources

• For setup information, see the "Sales Insights" chapter in the Implementing Sales guide.
• For information on using Sales Insights, see the "Sales Insights" chapter in the Using Sales guide.

Sales Catalog

See Product Group Changes in Audit History

View the audit history of changes users make to Product Group fields. Administrators select which fields to track the audit history for, and then view the audit history report. For each change made, the audit history reports such information as:

• Field name
• Date and time of change
• Original field value
• New field value
• User who made the change

This feature lets you know the history of changes made to product group fields, and the specifics of those changes, for auditing and tracking purposes.

Steps to Enable

To enable and configure auditing on product groups, first enable auditing for the business object:

• Go to Navigator > Setup and Maintenance.
• Search for the task, Manage Audit Policies.
• Select Configure Business Object Attributes.
• From the Product list, select Sales Catalog.
• Check the objects to enable auditing for.
• Select the attributes to audit.
• Save your changes.

NOTE: Administrators must have the FND_MANAGE_SALES_AUDIT_POLICIES_PRIV privilege to do these steps.

To view product group audit reports:

• Go to Tools > Audit Reports.
• From the Product list, select Sales Catalog.
• Select the Business Object Type.
• Select other report filter criteria, as needed.
• Click Search.

NOTE: Users must have the FND_VIEW_SALES_AUDIT_HISTORY_PRIV privilege to view product group audit reports.

Tips And Considerations

• Use this feature to audit changes made to attributes of a product group, a product group product, and product group relation objects.
• This feature audits changes made within the Oracle Sales application specifically. It doesn't audit changes made to product groups within in the Oracle Product Information Management (PIM) module, including changes made in PIM that are synched to Sales.
• The Description field in the user interface refers to the product group reference number. This audit feature uniquely identifies product groups by the product group reference number, not by the product group name.
• Product eligibility rules associated with product groups are not audited this release
• The Product object isn't auditable in this release. Only product groups are currently audited.

Key Resources

• See the "Application Change Auditing" chapter in the Implementing Sales guide.

Role Information

• Sales Administrator

CX Sales Mobile

Embed Web Links to Custom Apps in the CX Sales Mobile App's Main Menu

You can add a web link to the CX Sales Mobile app's main menu that opens a custom web or mobile app when you tap the link. Once the web link is set up, it appears just like the other Sales objects in the main menu, so that it integrates seamlessly into the CX Sales Mobile app.

With linking to custom applications now available in the mobile app, field sales representatives have a more integrated experience when using the CX Sales Mobile app along with custom apps right on their mobile devices.

Steps to Enable

Leverage Application Composer to expose and adjust page layout and attributes. To learn more about extending your application using Application Composer, visit Oracle Help Center > your apps service area of interest > Books > Configuration and Extension.

Tips And Considerations

Enter Link Details

Key Resources

• See the "Embed Links to Custom Apps in the Main Menu" topic in the "Mobile Applications" chapter in the Implementing Sales guide.

Role Information

• Sales Administrator
• CRM Application Administrator

Collaborate on Opportunities Using Microsoft Teams

Let your salespeople collaborate on Microsoft Teams to advance the sales pipeline from their open opportunities. Directly from the opportunities page, salespeople can click the action to add all existing members of the opportunity to a team in Microsoft Teams and start collaborating.

Click Create Team in Microsoft Teams from the Opportunity Actions menu to create the team in Microsoft Teams.

Here is a sample of a team created in Microsoft Teams with opportunity members:

Steps to Enable

Complete the following setups: 

1. Setup Microsoft Teams for Sales. See the Setup Microsoft Teams for Sales topic to learn more.
2. Use Application Composer to add the following actions to the Opportunity Detail page layout and save your changes:
   • Create Team in Microsoft Teams: Add this action only to the user roles you want to allow.
   • Go to Microsoft Teams

Tips And Considerations

• The Opportunity owner must be a Microsoft Teams user and will be the owner of the team in Microsoft Teams.

• Any team member that is part of the Opportunity resource team and is a Microsoft Teams user will be added to the created team for the opportunity in Microsoft Teams.

  • Set the value of the Territory Based Resource Assignment Style profile option (MOO_OPTY_RESOURCE_TBA_STYLE) to specify if all members of the territory should be added to an opportunity team or just the owner. The default is to add all members to the opportunity team.

• In order to map a CX Sales user to the user account in Microsoft Teams, the user's primary email address under their resource profile in CX Sales must match the user's email address in Microsoft Teams.

Key Resources

See this content:

• The "Microsoft Teams" chapter in the Implementing Sales guide.
• The "Opportunity Team Members" section of the "Opportunity" chapter in the Using Sales guide.

Role Information

This feature is available to all roles, primarily for sales representatives and managers.

Sales Analytics

Secure Product Group Visibility in Reports Based on Access Groups

User visibility to product group data in Oracle Transactional Business Intelligence (OTBI) reports is based on access groups defined for product groups. To provide visibility to users while giving organizations control of who sees what, users now only see in reports the product groups that they have permissions to view.

With access group setup, users can only see in reports the product groups that they have access to as defined by access groups. This is helpful when there are different groups of users who should have access to different product groups.

Steps to Enable

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

Key Resources

• See the What’s New for Update 21C, item “Use Access Groups to Configure Data Security for Products, Product Groups, and Price Books”.
• Also see the “Use Access Groups to Secure Product, Product Group, and Price Book Data” topic in the "Access Groups" chapter in the Securing CX Sales and B2B Service guide.

Role Information

• Sales Administrator
• Sales Manager
• Sales Representative

Use Business Intelligence Cloud Connector View Objects for Incentive Compensation Payment Reporting

The new Business Intelligence (BI) Cloud Connector view objects let you extract data for:

• Subledger
• Paysheets
• Payruns
• Pay Groups
• Payment Plans
• Plan Component Formulas
• Participant Pay
• Interval Types

You can use this feature for high-volume data extraction and for extracting data for use in data warehouses or other tools.

Steps to Enable

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

Key Resources

• See the Oracle BI Cloud Connector Console documentation.

New Dimensions Added to Asset Contact Subject Area

These new dimensions have been added to the Asset Contact subject area:

• Product
• Customer
• Employee Dimensions

To improve performance and to avoid cross-subject-area queries, the Sales - CRM Asset Contact subject area has been enhanced by adding the Customer, Product, and Employee dimensions.

Steps to Enable

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

Key Resources

• See the "Asset Contact" section in the Subject Areas for Transactional Business Intelligence guide.

Sales Product Information Master Reporting Enhancements

Sales Product Information Master reporting enhancements include the addition of reporting on new product number of processing days to support Oracle Configure, Price, and Quote (Oracle CPQ) needs.

The additional attributes in the Sales - CRM Quote Lines - Product and Sales - CRM Pipeline - Product subject areas are:

• Configurable
• Default Periodicity
• Default Periods
• Default Price Type
• Processing Days

Using Application Composer, you can expose these five new attributes on the Products pages, letting Sales users ensure that additional address attributes from products introduced as part of the Sales Product Information Master enhancements are available in the Product dimension for reporting purposes.

Steps to Enable

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

Tips And Considerations

The Sales Product Information Master is the product master for Oracle CPQ.

Key Resources

• See the subject areas related to products in the Subject Areas for Transactional Business Intelligence guide.

Disable Data Collection for Application Usage Insights

Capabilities to optionally disable the harvesting and collection of usage data in Application Usage Insights are extended. In a previous release, the ORA_ZCA_CH_DISABLE profile option was introduced to disable the collection and storage of click history data. In Update 21D, this profile option also disables the collection and display of any data appearing in Application Usage Insights, including data for user logins, session duration, object usage, click history, and more. Usage data also won't appear in Application Usage Insights dashboards.

This feature is important for organizations that don't want to collect, store, or display usage data supported by Application Usage Insights. This profile option is disabled by default; you must enable it to stop the collection of usage data.

Organizations that don't want to collect data about their end users' usage of the Sales application will find this feature useful. This profile option lets those organizations disable the collection of a broader set of usage data.

Steps to Enable

Enable the ORA_ZCA_CH_DISABLE profile option.

Key Resources

• See the "Application Usage Insights" section in the "Application Adoption and Usage Reporting" chapter in the Creating and Administering Analytics guide.

Role Information

Sales Administrator

View User Adoption of Custom Objects in Application Usage Insights

Custom objects are now available in Application Usage Insights. This feature shows the usage of custom objects by sales teams, complementing the usage of standard objects already supported in previous releases. Metrics such as the number of custom object records created and updated are supported. Administrators can configure which custom objects to expose or hide to sales team members.

Sales managers can understand which individuals on their teams are adding records to and updating records in custom objects. These newly added insights enable sales managers to determine if team members are adhering to expected sales processes that involve custom objects. This also enables sales managers to correlate user adoption to business success goals, and provides insights for coaching opportunities.

Steps to Enable

In order to select and expose custom objects in Application Usage Insights, an administrator must select them in the Configuration area, which is exposed by a security privilege.

1. Enable the ORA_ZCA_APPLICATION_USAGE_INSIGHTS_MANAGE_CUSTOM_OBJECTS privilege for the Sales Administrator. This will expose the Configuration link within the Record Usage area of the application drop-down menu.
2. As an administrator:
   1. Go to the Application Usage Insights application.
   2. Navigate to the hamburger drop-down menu and select Record Usage > Configuration > Select Custom Objects.
   3. Select one or more custom objects to expose in the Object Record Reporting window. 
   4. After selecting the custom objects, click OK. 
3. For an end -user to view reports on custom object usage:
   1. Navigate to the application hamburger drop-down menu and select Record Usage > Custom Object Records.
   2. Select the custom object in the Custom Object drop-down list to report on.

Key Resources

• See the "Application Usage Insights" section in the "Application Adoption and Usage Reporting" chapter in the Creating and Administering Analytics guide.

Role Information

• Sales Administrator
• Sales Manager

Sales Force Automation

Customer Data Management

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.

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.

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 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.

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.

Oracle Sales Assistant

Configure Fields to Prompt for Values when Creating Records Using Oracle Sales Assistant in Microsoft Teams

You can select which fields that you want Oracle Sales Assistant to request a response for when conversationally creating a record using the Microsoft Teams or CX Sales Mobile Application Composer tool. Oracle Sales Assistant only prompts for values of mandatory fields that have no default values.

Prompted Fields on Assistant Create section in Oracle Sales Assistant for Microsoft Teams composer

Prompted Fields on Assistant Create section in CX Sales Mobile composer

NOTE: If you need help with enabling Oracle Sales Assistant, send us a message on the Sales Assistant forum on Oracle Cloud Customer Connect.

Using the search and select feature from the Microsoft Teams or CX Sales Mobile Application Composer tool, you can assign additional fields that you want the user to answer questions when conversationally creating a record.

Steps to Enable

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

Key Resources

• See the "Sales Assistant" chapters in the Implementing Sales guide and in the Using Sales guide.

Role Information

• Sales Administrators

Modify Sales Briefing and Pipeline Global Actions Using Microsoft Teams Composer

If users ask Oracle Sales Assistant for a daily sales briefing in Microsoft Teams, the assistant responds with the number of opportunities in the pipeline, number of tasks due today, and appointments upcoming today. Using the Microsoft Teams Composer tool in Application Composer, you can modify the content of the sales briefing response for your users. For example, you may want to hide details of today's upcoming appointments. In addition, you can also select the saved search list that contains the definition of the sales pipeline, and you can modify the definition to suit your company requirements. The definition is then used for both sales briefing and when salespeople directly ask for their sales pipeline.

Customize Sales Briefing and Pipeline via "Global Actions" Feature in Oracle Sales Assistant for Microsoft Teams composer

NOTE: If you need help enabling Oracle Sales Assistant, send us a message on the Sales Assistant forum on Oracle Cloud Customer Connect.

This feature lets you define customized sales briefing cards, as well as define the correct definition of pipeline for each of your company's roles.

Steps to Enable

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

Tips And Considerations

• To modify the sales briefing card and the pipeline definition, from Oracle Sales Assistant for Microsoft Teams composer, click the Global Actions icon, then create a custom layout.
• You can create assign roles to each custom layout.

Key Resources

• See the "Sales Assistant" chapters in the Using Sales guide and in the Implementing Sales guide.

Show User Relevancy and Context Records when Asking Oracle Sales Assistant for a Record

When you ask Oracle Sales Assistant for a record to view or act on, such as View the Vision Corp opportunity, the set of matching records returned are the ones that are most relevant to you. However, if  you can't find the record you want within this set, then you can expand and see matches from within your full set of accessible records for the specific object type.

NOTE: If you need help with enabling Oracle Sales Assistant, send us a message on the Sales Assistant forum on Oracle Cloud Customer Connect.

This feature allows most relevant records to be surfaced to your users so that they can easily view and act on the record they are searching for.

Steps to Enable

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

Tips And Considerations

• This feature applies to all Oracle Sales Assistant supported channels.

Key Resources

• See the "Lists of Prioritized Recent Items" section of the "Adaptive Search and Workspace" chapter in the Implementing Sales guide.
• See the "Sales Assistant" chapters in the Using Sales guide and in the Implementing Sales guide.

Role Information

This feature can be used by any users who have access to sales assistant on the different channels.

Enterprise Contracts

Print Standard and Custom Attributes in Deviation Reports

You can print standard contract attributes, custom attributes, and descriptive flexfields in deviation reports. The deviation data model XML provides the list of attributes that you can use to configure these reports in Oracle Business Intelligence Publisher:

• SupplierContractDeviations.rtf
• CustomerContractDeviations.rtf

Attributes added in the RTF templates will be reflected in PDF reports also.

From the Review Deviation Report UI, you can download the RTF report, PDF report and deviation data model XML of the specific contract. The data model XML has the tags which can be used to customize the deviation reports. 

Standard attributes related to sourcing and purchasing can be added in the SupplierContractDeviations.rtf. The PDF and RTF reports and the data model XML are available in the Procurement application from Negotiations, Purchase Agreements and Purchase Orders UIs.

Review Contract Deviations UI

Use the opt-in Print Standard and Custom Attributes in Deviation Reports to enable this feature.

You can view the PDF report before activating the contract. Adding additional attributes related to the contract provide better context about the deviations to the approver and helps in the approval process.

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: Enterprise Contracts

Key Resources

• See the "Approve and Accept Customer Contracts" chapter in the Using Customer Contracts guide.

Protect System Variable Edits in Microsoft Word

You can add system variables and view the value for these variables in your contract. You can’t save edits to system variables using the Oracle Contracts Microsoft Word add-in back to the application, but you can delete them. To delete a system variable, you must delete the content control of a system variable.

The application displays an error when you try to edit a system variable using the Microsoft Word document. System variables should be updated directly in the application to reflect in the word document.

Error Message When Editing System Variable

This feature improves the user experience when editing contracts in Microsoft Word.

Steps to Enable

You must download the latest Microsoft Word add-in from Contracts -> Terms Tab -> Actions Button -> Download Add-in for Microsoft Word Add-in.

Key Resources

• See the "Author Contract Terms" chapter in the Using Customer Contracts guide.

Use Problem Resolution in Contract Validation Messages

When you validate a contract, more meaningful and informative validation error and warning details are provided in the Validation Results page to help you resolve any contract validation issues. For example, additional information might include what caused the problem and how and where to fix the issue so that the validation of the contract can proceed. You can also view these validation details when you validate the contract from the contract wizard.

Validation Contract UI Displaying Problem Resolution

This feature helps you fix contract validation errors more effectively.

Steps to Enable

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

Use Enterprise Contracts in Business Intelligence Cloud Connector

You can use Oracle Business Intelligence (BI) Cloud Connector to extract the BI data from Enterprise Contracts. Here are the contract objects you can use in BI Cloud Connector:

• Contracts
• Contract Translations
• Contract Custom Extensions
• Contract Approval History
• Contract Signature History
• Contract Status History
• Related Contracts
• Contract Parties
• Contract Party Contacts
• Contract Sales Credits
• Contract Fulfillments
• Contract Fulfillment Notifications
• Contract Fulfillment Translations
• Contract Risks
• Contract Lines
• Contract Line Translations

You can search for the objects to extract in the BI Cloud Connector Console.

BI Cloud Connector Console

For each object, you can edit a query and select columns to isolate the data to be extracted.

Query Columns for an Object

This feature lets you export the contract data for analysis.

Steps to Enable

Make the feature accessible by assigning or updating privileges and/or job roles. Details are provided in the Role section below.

Key Resources

• See the Oracle BI Cloud Connector Console documentation.

Role Information

Update the security privileges for users who require access to BI Cloud Connector (BICC). Refer to Provision Access.

Sales for Microsoft 365

Enable Auto-synchronization of Business-relevant Appointments Between Microsoft 365 and CX Sales

Business-relevant appointments are automatically synced between Microsoft 365 and Sales, thus improving user productivity by eliminating a saved-search-based approach.

All relevant appointment data is available in Sales automatically for reference and analytics.

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

Tips And Considerations

Enable the "Auto Capture Appointments" check box to enable this feature. 

Additionaly enable the "Enable Blocked Time" check box to enable capturing of blocked time for all users.

Key Resources

• See the "Microsoft 365" chapter in the Implementing Sales guide.

Intelligent Advisor

Interview Restyling Extended to Include Accessibility

Additional tags have been added to the list of allowed attributes for style extensions for a subset of interview control types.

This feature enables groups of controls in interviews to meet accessibility requirements, and opens up additional avenues for customization.

Steps to Enable

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

Key Resources

• Allowed additional attributes for style extensions for controls

Role Information

• Interview developers

Compare and Merge Project Versions

Users can now compare two policy models for a change-by-change breakdown of where the differences between the two versions have occurred.

This allows authors to easily find changes made in a production branch since the time it was branched off the main development project, and pull them into the current development branch.

Steps to Enable

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

Tips And Considerations

To see what has changed between two old versions, you can download one old version, and compare it to the other old version still in Intelligent Advisor Hub.

Key Resources

• Compare Project Versions

Role Information

• Authors

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.