This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Module | Feature | Notes |
|---|---|---|---|
| 14 NOV 2022 | Search | My Smart List Saved Searches Renamed to My List |
Removed feature from update 22D. |
| 14 SEP 2022 | Created initial document. |
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.
Column Definitions:
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. |
Customer Must Take Action 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 |
|
||
Manage and Use Custom Territory Attributes for Territory-Based Assignments |
||||||
View and Search Dynamic Choice List Field Values Based on Resource Object |
||||||
Click Refresh Icon in Workspace to View Latest Search Results |
||||||
Use Domestic and Global Ultimate Oracle DataFox Identifiers in Account Import |
||||||
Use Hierarchy-Related Top Account and Oracle DataFox Identifiers in Accounts REST API |
||||||
Use Consistent Attribute Mapping When Enriching Accounts and Contacts Through Different Applications |
||||||
Assign a Customer Profile Quality Score to Account Records Based on Configurable Scoring Logic |
||||||
Support Purged Worker Sync Using the Maintain Party and Location Current Record Information Scheduled Process
Use the Maintain Party and Location Current Record Information scheduled process to sync purged worker type records in Human Capital Management (HCM) to Customer Data Management person party records. In HCM, terminated and canceled hire persons can be purged using Remove Person. These, when synced into person parties, ensure that synched details like name (first, middle, last), and contact (phone, email) are deleted or masked based on update in HCM.
The employee and contingent worker related usages on the person party record are also end dated, if still active. In a scenario where a person party doesn't have other active usages, even the person party is inactivated.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See the "Maintain Party and Location Current Record Information" topic in "Sales and B2B Service Scheduled Processes" chapter in the Understanding Scheduled Processes guide.
Purge Inactive Sales Households
Purge household data from your test and production instances, rather than retaining the information in an inactive state. You can purge these records to adhere to data protection regulations and as part of housekeeping activities.
You can purge records based on filter criteria that you specify for the newly supported Household object.
Steps to Enable
Set the existing purge profile options to enable the purge functionality. The purge functionality is disabled by default.
Key Resources
- See the "Purge Inactive Party Records" topic in the in the "Sales and B2B Service Scheduled Processes" chapter in the Understanding Scheduled Processes guide.
Manage and Use Custom Territory Attributes for Territory-Based Assignments
Sales operations teams can assign territories using custom territory attributes. For example, organizations might want to track revenue by different groups of sales representatives within their territories. One group might focus on new customers while another group focuses on renewal of current subscriptions. Using the custom attribute territory feature, you can separately track revenue for both groups of sales representatives. This means that records are matched with the revenue based on a new territory or a renewal territory.
You now have more flexibility to use territory-based assignment by creating custom territory attributes or custom dimensions.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See the "Configure and Extend Application Pages for Territories" topic in the "Extend Territory Management" chapter in the sales Implementation Reference guide.
Role And Privileges
- Sales Administrator
Expand Scheduling Options for Routines
You can now schedule routines to run hourly. Hourly routines are limited to 250 records per run. This option is available to all administrators with access to routines.
You can also schedule routines to run across all data for an object. You must assign the privilege, ZCA_SCHEDULE_ROUTINE_APPID, to an administrator. Once assigned, the administrator will see the option during routine creation.
Providing more scheduling options gives you more flexibility to run routines. For example:
- You can use an hourly option when you need to run a routine several times within a day. This option is available to anyone with access to Routines.
- You can assign a privilege to administrators to allow them to run a routine across all data for an object. This is useful if you need to enforce processes across regions managed by different administrators and you don't want to create a separate routine for each region.
Steps to Enable
Make the feature accessible by assigning or updating privileges and/or job roles. Details are provided in the Role section below.
To use this feature, you must have the appropriate privileges and job roles.
- You must already have access to Routines via the privilege, ZCA_MANAGE_ROUTINES.
- Assign the privilege, ZCA_SCHEDULE_ROUTINE_APPID, to the desired role.
During routine creation, the trigger step will have an option to schedule the routine to run across all data.
Tips And Considerations
You can't toggle the option to run a routine across all data. For example, once set, the routine will always run across all data.
Key Resources
- See the "Routines" chapter in the Implementing Sales guide.
Role And Privileges
The ability to manage routines is configured for the following roles:
- Application Implementation Consultant
- Sales Administrator
- Customer Relationship Management Application Administrator
The Routines dashboard now has an option to run on demand. Use this option to run a routine immediately when you need to view the results or to re-run a routine after correcting errors.
Run a routine to schedule a one-off run. This is useful during testing on when a routine has errors and needs to run prior to the next recurring period.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See the "Routines" chapter in the Implementing Sales guide.
Role And Privileges
- Sales Administrator
Create Quote from an Opportunity Automatically
You can enable the automatic creation of a quote in Oracle Configure, Price, and Quote (Oracle CPQ) from an opportunity by using rules so that salespeople can access the quote directly without having to manually create it.
This feature lets you automate the process of creating quotes from opportunities based on predefined rules.
Steps to Enable
- Assign administrative privileges to an Oracle CPQ user to allow the automatic creation of a quote from an opportunity.
- Set up the CX Sales to Oracle CPQ configuration. See the CX Sales Configuration Steps topic in the Integrating CX Sales with Oracle CPQ guide.
- Go to the Manage Oracle CX Sales to Oracle CPQ Cloud Integration page and complete these steps:
- Click the Set Up link under the Authorization column.
- Select oracle/wss_username_token_over_ssl_client_policy for Security Policy.
- Enter the user name and password for Single Sign-on.
- Set up routines on the Opportunity object, select the Create Quote action, and define the rules. See the Overview of Routines topic to learn more.
Key Resources
- See the "Enable Creating a Quote Automatically from an Opportunity" topic in the "Quotes and Orders" chapter in the Implementing Sales guide.
Role And Privileges
- Sales Administrator for the setup and error handling.
- Salespeople and sales managers for using the quotes to move the deal to closure.
View and Search Dynamic Choice List Field Values Based on Resource Object
You can view, search, and add filters on all dynamic choice list fields for the Resource object using Adaptive Search. A dynamic choice list is a field that contains a list of values that are populated from the actual data of another object. This feature lets you use resource-based filters to return a set of search records that best suits your requirements.
This feature lets you view and search on values of dynamic choice list fields that are based on the Resource object.
Steps to Enable
No steps are required to enable this feature.
Key Resources
- See the "Workspace and Work Areas Search" chapter in the Using Sales guide.
Role And Privileges
- Workspace and Adaptive Search users
Click Refresh Icon in Workspace to View Latest Search Results
Users can now simply click the new Refresh icon in Workspace to get the latest data in Workspace without having to reload their browser page.
This enhancement improves the user's experience while working with Workspace.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See the "Workspace and Work Areas Search" chapter in the Using Sales guide.
Role And Privileges
- Workspace and Adaptive Search users
Use Domestic and Global Ultimate Oracle DataFox Identifiers in Account Import
Use additional account hierarchy information, such as top hierarchy account, and identifiers from Oracle DataFox, such as domestic ultimate and global ultimate identifier, in Account Import Management.
Here are the new attributes for the Account import object that provide additional information on an account hierarchy:
- DomesticUltimateDatafoxId
- GlobalUltimateDatafoxId
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See the "Accounts" section in the Understanding Import and Export Management for CX Sales and B2B Service guide.
Use Hierarchy-Related Top Account and Oracle DataFox Identifiers in Accounts REST API
Use additional account hierarchy information, such as top hierarchy account, and identifiers from Oracle DataFox, such as domestic ultimate and global ultimate identifier, in the Accounts REST API.
Here are the new attributes exposed on the Accounts REST API:
- TotalAccountsInHierarchy
- TotalChildAccounts
- ParentAccountList
- PrimaryContactDoEmailFlag
- PrimaryContactDoCallFlag
- TotalImmediateChildAccounts
- UltimateParentFlag
- GlobalUltimateFlag
- DomesticUltimateFlag
- UltimateIdentifierSource
- DomesticUltimateDatafoxId (editable)
- GlobalUltimateDatafoxId (editable)
- ProfileQualityScore
Most of the fields are read-only, except the ones marked as editable. The read-only fields are calculated, derived, or auto-populated from system processes.
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 REST API for CX Sales and B2B Service guide.
Account and Contact Enrichment
Use Consistent Attribute Mapping When Enriching Accounts and Contacts Through Different Applications
Use a single, consistent attribute mapping for all CX Sales enrichment processes. The attributes get enriched during smart data, real-time or batch enrichment, and sync operations. You can manage the single mapping using the Manage Oracle Data as a Service Attribute Mapping and Preferences task for all enrichment processes in CX Sales.
You can now manage a single mapping for all enrichment integration flows, namely smart data for account, real-time and batch enrichment, and sync. You can map account custom attributes to Oracle Data as a Service (Oracle DaaS) fields once, and their values will be saved in each enrichment flow. You can customize any CX Sales map defined in Oracle DaaS and use it for enrichment of accounts or contacts.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- You can only have one map active at a time in CX Sales for account enrichment. Similarly, only one map can be active in CX Sales for contact enrichment. The active map is used for smart data, real-time enrichment and sync, and batch enrichment and sync.
- You must first define an account or contact map in Oracle DaaS, of template type Sales and Service, for it to be available in CX Sales for use and customization.
- Select a sales attribute to map it to the applicable source attribute. For example, the current release only supports Oracle DaaS as the source. Not all Oracle DaaS source attributes can be mapped.
- If the sales attribute supports additional preferences like Don't Overwrite, Don't Apply Blank Values, and Display During Real-time Enrichment, then these options are enabled after mapping the attribute, and you can select desired option value. If a mapped attribute doesn't support these preferences, then these options will be disabled.
- Resetting the map will remove all customization, and revert the setting to use the default map, CXCompany or CXContact.
- Existing customization in existing maps will be migrated to new maps, CXCompany and CXContact during upgrade. Enrichment will work as expected after the upgrade, after incorporating existing customizations, and no manual configuration is required for the upgrade.
Key Resources
- See the "Configure Data Enrichment" chapter in the Getting Started with Your Customer Data Management (CDM) Implementation guide.
Role And Privileges
- Master Data Management Application Administrator
Assign a Customer Profile Quality Score to Account Records Based on Configurable Scoring Logic
Configure a score based on the completeness and attribute values of a customer profile. You can then use a batch process to assign and maintain the score as an attribute of the account profile.
This feature gives you these benefits:
- Users can easily review, sort, and filter account records based on the completeness and quality of their profile records.
- The customer profile quality score lets you quickly identify customer data quality issues and to rationalize data stewardship processes and resources.
- Prioritize and stage sales activities based on the confidence and quality of the customer profile data.
Steps to Enable
Configure and Activate a Scoring Model
- Navigate to Application Composer outside of a sandbox (mainline mode).
- Click the Customer Profile Quality Configuration link in the Common Setup area of the navigation panel.
- Use the Customer Profile Quality Configuration guided process to define a profile quality scoring model.
Activating the scoring model is the final step of the Customer Profile Quality Configuration guided process.
Expose the Score in the Sales Application
- Enable the Account - Profile Quality Score attribute in Adaptive Search.
- The Profile Quality Score attribute is exposed in Application Composer and the Accounts REST resource.
Tips And Considerations
When you activate a customer profile quality score configuration, a recurring scheduled process with a daily frequency is automatically submitted to run the scoring job on your account records. To change the frequency of the scheduled process, use the standard Scheduled Process interface to define and submit a new Schedule Scoring Process job.
Key Resources
See this content:
- Implementing Customer Data Management guide to learn more about the Customer Profile Quality Score feature
- Refer to the Oracle Sales REST API guide to learn more about the scoringModels REST resource
Role And Privileges
- Users with the Master Data Management Application Administrator job role can define and activate customer profile quality configurations.
- If you have created custom roles based on Master Data Management Application Administrator that you want to be able to manage profile quality scoring configuration, you can add the ZCH_MANAGE_SCORING_MODEL_PRIV to those roles' privileges.
- All users with access to the Accounts business object in Oracle Sales can access the calculated Profile Quality Score attribute of the account record