FEBRUARY MAINTENANCE PACK FOR 23A

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	Module	Feature	Notes
16 JAN 2023			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

Application Composer

Create Smart Actions Using Guided Process

You can now create smart actions more easily using a guided process that's specific to the type of action you're creating, such as an action based on a REST API or UI.

Admin can use guided process to create a smart action which is easy to follow and shows fields related to the flow

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.

CRM Common Components

Create Routines from Predefined Templates

You can create routines from predefined templates. Templates help you configure routines quickly by providing examples for such items as opportunity follow-up or past due tasks.

Sales administrators can get started quickly with templates provided by Routines. In some cases, rules may not always be apparent to administrators, for example, past due tasks require knowledge of ActivityFunctionCode and the allowed values.

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

Specify Child Objects in Routine Rules

Sales administrators frequently need to evaluate child objects to determine if an action should be taken. For example, you might want to select opportunities based on values in revenue tables. Rules for child objects can be entered by clicking the Add Dependent Rule button and are available for Accounts, Contacts, Sales Leads, and Opportunities.

Specifying child objects rules in routines helps to ensure the accuracy of data and helps determine if any further actions are required. For example, you might want to set up dependent rules for all qualified leads without opportunities.

Steps to Enable

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

Tips And Considerations

Rules for child objects can be entered by clicking the Add Dependent Rule button and is available for the following objects:

• Account
• Contact
• Sales Lead
• Opportunity

Key Resources

See the "Routines" chapter in the Implementing Sales guide.

Role And Privileges

• Sales Administrator

Update 23A

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	Module	Feature	Notes
14 DEC 2022			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

CX Foundation

Capture Interactions in Activities

Salespeople can now log Interactions as part of Activities. They can log and view historical interactions and associate them with an activity. If there's an activity created to make a call or to send an email to a customer, the salespeople can capture corresponding details of the call or email interactions in the Interactions History subtab under the activity record.

This feature helps salespeople manually log interactions directly from activity records.

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

Prerequisites:

• Set the profile option, ORA_ZCA_ENABLE_TRACKING_INTERACTIONS, to Y at the Site level.
• The new privilege, ZCM_MANAGE_SALES_INTERACTIONS, must be assigned to the user.

Opt-In Instructions:

• Customers need to set the profile option, ORA_ZCA_ENABLE_INTERACTIONS_CALL_WRAP_UPS, to Y, so that call wrap-up tracking is enabled.
  • Assign the privilege ZCM_MANAGE_INTERACTIONS to give access to manually log interactions from the Interactions history subtab from Activities. 
  • Once the customer sets the profile option to Y, it shouldn't be reverted back to the old model.

• For CX Sales users, when the profile option is enabled, the CX Sales web application should:
  • In Workspace, the saved searches 'My Call Reports' should not be available from Activities
  • In Workspace, 'Create Call Report' and 'Decline Call Report Creation' smart action in 'My Appointments' and 'My Calls to Log' saved search should be hidden 
  • In the 'My Activities' page, 'My Call Reports' list should be hidden
  • Hide the 'Call Report' subtab in the Appointments/Tasks pages
  • Hide 'Create Call Report' from the Actions menu in Appointments page
  • Enable 'Log an Interaction' smart action in action menus on all objects that previously had 'Create Call Report'
  • Enable 'Interactions History' subtab in Activities
  • If the customer uses custom layouts, actions related to Call Reports should be updated to disable Call Report action

Steps to enable the Interactions History subtab:

One can view interactions history associated with their activities through the Edit Task: Interactions History subtab and Edit Appointment: Interactions History subtab.

The Interactions History subtab is hidden by default, but one can make it available to users through Application Composer.

Here's how to add the Interactions History subtab to the Edit Activity page.

1. Sign in as a sales administrator or as a setup user.
2. Activate a sandbox.
3. Navigate to Application Composer, in the Configuration category.
4. In the navigation tree, expand Standard Objects, expand Activities, and click Pages.
5. Ensure that the Application Pages tab is selected.
6. In the Details Page Layouts region, there are two options, one for Task and another for Appointment. Duplicate the standard layout by highlighting the standard layout and clicking the Duplicate icon.
7. Type a new layout name and click Save and Edit.

The Details Layout page appears in the Task/Appointment section.

8. On opening the new layout page, in the Subtabs Region, click the Hide, Show, or Reorder Subtabs icon.

The Configure Subtabs dialog box appears.

9. Move Interactions History from the Available Subtabs to the Selected Subtabs window.
10. Click OK.
11. Click Save and Close.
12. Click Done and ensure that the layout status for your user-defined layout is Active.
13. Test the changes: Navigate to Sales > Activities as a user with access to the Activities pages, for example, as a salesperson. Edit a task or an appointment and ensure you can see the Interactions History sub-tab in the Edit Activity page.
14. Publish the sandbox.

Tips And Considerations

Customers should go into the Smart Actions framework and disable all the Call Report actions and enable all the Log an Interaction actions manually. Same goes for Saved searches. Failing to do this will result in both call report and Interactions functionality not being available from the application.

Role And Privileges

Sales Representative

CRM Common Components

Receive Email Notifications for Scheduled Jobs

If a scheduled job, such as Periodic Refresh, runs beyond a predefined threshold, then you get an email notification to inform you.

This helps you monitor jobs without having to sign into the application.

Steps to Enable

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

Key Resources

• See the "Workspace and Adaptive Search" chapter in the sales Implementation Reference guide.

Automatically Create Proposals from Opportunity Quotes

Proposals can automatically be generated from opportunity quotes by utilizing the power of routines that use configured rules. This extends the existing capability, which automatically creates a quote from an opportunity using routines.

Salespeople don't need to manually go through the process of generating a proposal. After the administrator sets up the routine rules on quote attributes and when the rule conditions are met, the proposal is automatically created and added to the quote. Salespeople can then view the proposal in CX Sales or Oracle Configure, Price, and Quote (Oracle CPQ) and take the next steps to close the deal. Salespeople are thus able to focus time on negotiating and closing deals with the customer, instead of spending time on manual nonvalue-added tasks, such as creating a proposal manually.

Steps to Enable

1. Assign administrative privileges to an Oracle Configure, Price, and Quotes (Oracle CPQ) user to allow the automatic creation of a proposal from a quote.
2. 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.
3. Go to the Manage Oracle CX Sales to Oracle CPQ Cloud Integration page and complete these steps: 
   1. Click the Set Up link under the Authorization column.
   2. Select oracle/wss_username_token_over_ssl_client_policy for Security Policy.
   3. Enter the user name and password for single sign-on.
4. Set up routines on the Quote and Order object, select the Create Proposal 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 sales Implementation Reference guide.

Role And Privileges

• Sales Administrator for the setup and error handling.
• Salespeople and sales managers for using the proposals to move the deal to closure.

Enable User Context for Custom Objects

Administrators can now perform relevancy scoring calculations for custom objects. This allows for having relevancy-based saved searches in Adaptive Search, which helps to view the list of most relevant items from those custom objects in Workspace, Digital Sales, and CX Sales Mobile.

About 50 percent of Oracle customer data is built upon custom objects. This feature enhancement provides support for custom objects in User Context, thus providing better coverage of the feature in the product.

Steps to Enable

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

Tips And Considerations

This can be done only via REST APIs. 

Role And Privileges

• Administrator roles

Accounts and Contacts

Switch to New Rollups from the Existing Aggregate Fields of Workspace

Your users now get a more consistent user experience and improved performance because Workspace aggregate fields are now available as predefined rollups in the Rollups framework.

A standardized process to manage and calculate aggregated information ensures all metrics that are deployed across the application are consistent, accurate, and performant.

Steps to Enable

Here’s a summary of the privileges, setups, and tasks involved in setting up rollups for Sales:

1. Add the Manage Rollup Metrics privilege to a copy of the Sales Administrator job role (ORA_ZBS_SALES_ADMINISTRATOR_JOB).
2. Enable the Rollup Test Enabled profile option (ORA_ZCA_TEST_ROLLUPS), to display the Test tab on the Rollups setup page.
3. Verify that these scheduled processes appear on the Scheduled Process page:

• Rollup Full Refresh
• Rollup Hierarchy Refresh
• Rollup Incremental Refresh

4. Enable rollups for Adaptive Search. Let salespeople search accounts or contacts using rollups as search criteria.

Key Resources

• To learn how to implement rollups for your organization, see the "Rollups" chapter in the Implementing Sales guide.

Role And Privileges

• Sales Administrator

Search

My Smart List Saved Searches Renamed to My List

The "My Smart List" saved searches are now renamed to "My List". For example, the My Smart List for accounts is now renamed to My List for Accounts, the My Smart List for leads is now called My List for Leads, and so on.

The My List saved search shows relevant results based on a user's activity, and it includes the most recently and frequently accessed records.

Steps to Enable

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

Key Resources

• See the My Lists topic in the "Search" chapter of the Implementing Sales guide.

• See the "Workspace and Work Areas Search" chapter in the Using Sales guide.

Role And Privileges

• Workspace and Adaptive Search users

Application Composer

Display Smart Actions Based on Signed-in User

Configure a smart action to check for the signed-in user before displaying at runtime. This is helpful if certain users don't need to see a smart action.

Create smart actions that can be displayed based on the signed-in user.

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.

To configure a smart action to check for the signed-in user, add this to the smart action condition:

$AssigneePartyId != :SIGNED_IN_USER

Key Resources

• See the "Overview of Smart Actions" topic in the "Add Objects and Fields" chapter of the Configuring Applications Using Application Composer guide.

Allow Indexing of Custom Fields Not Yet Indexed

In Application Composer, you can now edit an existing custom field and index it for better search results.

Administrators can now index previously created custom fields by editing them. This allows them to improve the search performance of the field, if required. Custom fields of type Number, Text, Currency, and Percentage can be edited to change a non-indexed field to an indexed field.

Steps to Enable

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

Role And Privileges

• Sales Administrator

Allow Duplicate Records for Many-to-Many Relationships

Specify whether duplicate records are allowed for many-to-many relationships. Users might want to enter duplicate records due to their own business requirements.

Administrators can decide if duplicate records are allowed for many-to-many relationships.

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.

To enable duplicate records for many-to-many relationships, select the Allow duplicate records check box when creating or editing a many-to-many relationship in Application Composer.

Key Resources

• See the "Many-to-Many Relationships" topic in the "Add Objects and Fields" chapter of the Configuring Applications Using Application Composer guide.

Security

Configure Territory-Based Custom Object Security Using Access Groups

Enable territory-based access to custom objects using a Territory dynamic choice list field and access groups. Once a territory is selected, a territory team member as well as other members of the territory hierarchy can access custom object records.

Customers no longer need to create custom data security predicates to secure custom objects based on a Territory dynamic choice list field.

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.

To use territory-based custom object security, first enable access group security and then enable the Configure Territory for Access Group Security in Application Composer. You should then configure access groups in Sales and Service Access Management, via the Navigator. You must still configure functional security using the Roles table in Application Composer.

Key Resources

• See the "Enable Territory-Based Access to Custom Objects" topic in the "Add Objects and Fields" chapter in the Configuring Applications Using Application Composer guide.

Role And Privileges

Sales Administrator

Import/Export Management

APIs

Find Deleted Records in Sales and Fusion Service Using Deleted Records API

You can now get a list of deleted object records in Sales and Fusion Service using the Deleted Records API, so that you can take appropriate actions in your application.

You can use this API to get the list of deleted object records if your integrated application needs the information.

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.

Role And Privileges

• Sales Administrator or Customer Relationship Management Application Administrator
• If you're going to use a custom role, make sure that your role has the View Deleted Object Records privilege.