- Revision History
- Overview
- Feature Summary
- Sales Automation Core Common
-
- CX Foundation
- CRM Common Components
-
- Use Adaptive Search and Workspace for Accounts and Contacts with No Setup
- Work Areas Powered by Adaptive Search Now Enabled Automatically for New Customers
- View Group By Date Buckets Beyond Last and Next 6 Months
- View the Adaptive Search Publish Job Progress
- Provide Enhancements to Quick and Advanced Subtabs for the Configure Adaptive Search Setup Tab
- Access Quick Actions from the Sales Tab
- Create Routines to Automate Repetitive Tasks
-
- Accounts, Contacts, and Households
- Security
- Import/Export Management
- APIs
- Customer Data Management
- IMPORTANT Actions and Considerations
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 |
|---|---|---|---|
| 20 DEC 2021 | 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.
Create Follow-Up Activities for External Appointments and Delete External Appointments
Create the follow-up activities such as the follow-up tasks, appointments, and call reports for external appointments synced from Microsoft 365. You can now delete external appointments as well.
Teams can track follow-up activities and call reports for appointments set up outside the company and shared with Sales from Microsoft 365. These are known as external appointments. Teams can also delete a shared external appointment when it's no longer relevant.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
See the "Activities and Calendar" chapter in the Using Sales guide.
Update Supplied and Custom Fields on External Appointments
When you sync an external appointment from Microsoft 365, the appointment is read-only when viewed from the web application. Even though the appointment is external to the company, you may want salespeople to be able to edit fields -- such as supplied fields like account, opportunity, and lead, or custom fields -- from the web application. As the administrator, you can enable the editing of appointment fields so that salespeople can edit both supplied and custom fields.
Keep in mind that meeting details, such as day, time, description, and location, will still be read-only, except in Outlook.
External appointments synced from Microsoft 365 should be linked to your Sales data to allow for tracking and analytics. While this is possible from Microsoft 365, the ability was not available from the web application. Now, the sales teams can update this key Sales and custom data from Microsoft 365 or the web application.
Steps to Enable
-
In the Setup and Maintenance work area, use the Manage Administrator Profile Values task:
- Offering: Sales
- Functional Area: Sales Foundation
- Task: Manage Administrator Profile Values
- On the Manage Administrator Profile Values page, search for External Appointments Editing Enabled (ORA_ZMM_ENABLE_EXTERNAL_APPT_EDIT) and set the Site value to Yes.
-
Save and Close the page.
Key Resources
See the "Activities" chapter in the Implementing Sales guide.
Get Reminded When a Task Is Due
Salespeople can now be reminded by email or get an alert in the Notifications area when their tasks are due. They simply configure the default reminder period in their user preferences. As an administrator, you can enable or disable the reminder notifications across the site and for individual users. You can specify whether to notify users via email, notifications, or both. You can configure the ORA_ZMM_TASK_DEFAULT_REMINDER profile option to set a default reminder period based on the task due date. For example, you can configure to send a notification three days before the task due date or when the task due date is reached.
Task due reminders improve efficiency and help teams reduce the risk of having pending tasks.
Steps to Enable
Setup 1: Set Profile Options
-
In the Setup and Maintenance work area, use the Manage Activity Profile Options task:
- Offering: Sales
- Functional Area: Sales Foundation
- Task: Manage Activity Profile Options
- On the Manage Activity Profile Options page, access and enable these profile options:
- ORA_ZMM_TASK_NOTIF_LIST_REMINDER: Enable to show task reminders in the Notifications area.
- ORA_ZMM_TASK_EMAIL_REMINDER: Enable to show task reminders by email.
- ORA_ZMM_TASK_DEFAULT_REMINDER: Set a default reminder period.
-
Save your changes.
Setup 2: Add Due Date Reminder Field to the UI
Here's how you enable the Due Date Reminder field to allow salespeople to set a reminder period.
- In an active sandbox, use Navigator to go to Configuration > Application Composer > Activity > Pages.
- Add the Due Date Reminder field to the Task Create and Task Details page layouts.
- Save your changes and publish the sandbox.
Key Resources
See "Get Reminded When a Task Is Due" in the "Activities" chapter in the Implementing Sales guide.
Role Information
- Sales Administrator
- Sales Representative
Use Adaptive Search and Workspace for Accounts and Contacts with No Setup
Oracle now enables Adaptive Search and the Workspace for accounts and contacts for all customers, even those who haven’t enabled Adaptive Search themselves. Oracle automatically runs the Publish process behind the scenes to index accounts and contacts for Adaptive Search. All salespeople see the Workspace icon on the home page and can use Workspace to manage accounts and contacts without additional setup.
Leverage the high performance Adaptive Search experience and use the intuitive Workspace UI to easily find and work with key sales-related information.
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.
Work Areas Powered by Adaptive Search Now Enabled Automatically for New Customers
New customers no longer have to opt in to get the high-performance Adaptive Search engine and other Workspace features for work areas tailored to many individual business objects. While the enhanced work areas are now available to new customers by default, existing customers must still opt in. The work areas that support the Adaptive Search and other Workspace features include:
- Accounts
- Activities
- Assets
- Campaigns
- Contacts
- Deal Registrations
- Leads
- Opportunities
- Partners
- Quotes and Orders
- Territories
Object work areas now provide much better search and filtering capabilities, and users experience a more consistent search experience across the work areas, Global Search, and Workspace.
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.
View Group By Date Buckets Beyond Last and Next 6 Months
Grouping of search results from Workspace is now more flexible. When filtering search records using Group By on a date field, salespeople can now select Month to group data into monthly intervals without the previous six-month restriction. Salespeople can view data beyond six months by simply clicking Show More. This provides a more complete view of data divided by months.
Flexible grouping of results by month provides improved flexibility and usability.
Steps to Enable
You don't need to do anything to enable this feature.
View the Adaptive Search Publish Job Progress
You can now view the real-time progress of Adaptive Search indexing jobs. When you click Publish, a progress bar indicates how much of the indexing job has been processed and what percentage remains before completion. This feature gives you better visibility on the Publish job progress so that you can plan your operations accordingly.
This feature gives administrators increased visibility into the Workspace and Adaptive Search Publish process.
Steps to Enable
You don't need to do anything to enable this feature.
Provide Enhancements to Quick and Advanced Subtabs for the Configure Adaptive Search Setup Tab
Adaptive Search configuration is now more intuitive and easier to set up. You can view and enable custom objects in Adaptive Search and Workspace from the Quick subtab of the Configure Adaptive Search Setup tab. In the Advanced subtab, you can view field names and their data types. The number of fields available for cross object searches is increased to 15 fields and can be specified by selecting the Include in Object Reference column for each field.
Search setup and configuration is more intuitive and flexible.
Steps to Enable
You don't need to do anything to enable this feature.
Access Quick Actions from the Sales Tab
Salespeople can now quickly create sales records from just one page. Using the Sales tab on the home page, salespeople can use quick actions to create their opportunities, leads, contacts, and activities, including tasks, appointments, and call reports, from a single location.
Quick actions available from the Sales tab of the home page reduce the number of navigational clicks and let salespeople quickly create various records and activities more efficiently.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
To edit or remove the out of the box quick actions, please see "Configure Quick Actions" topic in the "Home Page and Navigation" chapter in the Configuring and Extending Applications guide.
Key Resources
See this content:
- "Overview of the Main Navigation Components" in the "Before You Begin" chapter in the Implementing Sales guide
- "Overview of the Sales Application" in the "Get Started" chapter in the Using Sales guide
- "Configure Quick Actions" in the "Hope Page and Navigation" chapter in the Configuring and Extending Applications guide
Create Routines to Automate Repetitive Tasks
You can configure routines for business scenarios that help to improve the sales performance of your salespeople. For example, you might create a routine to alert users when opportunities are stuck and require attention to move them along the sales cycle. Routines can enforce data hygiene by discarding obsolete or outdated information, and they can reduce risk by providing timely and relevant reminders to focus on key customers.
The Routines feature helps administrators manage repetitive tasks, thereby improving efficiency. This feature also helps process compliance tasks to ensure users have accurate and current data.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
See the "Manage Routines" chapter in the Implementing Sales guide.
Role Information
Routines are configured by administrators with access to Application Composer. Access is controlled by the Manage Rouitnes (ZCA_MANAGE_ROUTINES) privilege. The privilege is assigned to the following roles:
- Application Implementation Consultant
- Customer Relationship Management Application Administrator
- Sales Administrator
Accounts, Contacts, and Households
Undo Enrichment for a CX Sales Account
Sometimes it's necessary to associate an account record with a new record through enrichment. Now you can undo the Oracle Account and Contact Enrichment by Dun & Bradstreet (formerly called Oracle Data as a Service or Oracle DaaS) enrichment that's been done for a Sales account record, so that you can re-create the association with Oracle Account and Contact Enrichment.
In certain scenarios, you may have to undo enrichment of an existing account and associate it again with Oracle Account and Contact Enrichment by Dun & Bradstreet (D&B) to get the right updates for your account. Let's see some examples.
- In the UK, when a private limited company goes public, D&B creates a new company record with a fresh DUNS number and obsoletes the old DUNS number and records of the company. In such a case, you have to restart the enrichment to get the latest updates for your account.
- In a rare case, enrichment can result in an incorrect operation and a Sales account is updated with incorrect D&B company data.
In such cases, you can undo the existing enrichment and redo it so that right data is updated in the Sales account records.
Steps to Enable
The undo enrichment feature is available for the accounts already enriched by D&B. Here's the setup:
-
In the Setup and Maintenance work area, use the Manage Data Enrichment Integration task:
- Offering: Sales
- Functional Area: Integrations
- Task: Manage Data Enrichment Integration
- On the Manage Data Enrichment Integration page, select Enable DaaS for Enrichment.
- Select Enable DaaS for SmartData.
- Enter the DaaS Credentials.
After configuring, your users can find the Undo enrichment option in the Actions menu of the Edit Account page.
Note: The Undo Enrichment option is available only for Oracle Account and Contact Enrichment by Dun & Bradstreet (D&B) enriched accounts. This option isn't available for the accounts that are not yet enriched or enriched only by Oracle DataFox.
Tips And Considerations
After you undo the enrichment, your account unlinks from Oracle Account and Contact Enrichment by Dun & Bradstreet (D&B), but the old data remains. Redo the enrichment so that the latest data from Oracle Account and Contact Enrichment by Dun & Bradstreet (D&B) replaces the old data.
Note: The enrichment sync jobs won't run for accounts unlinked from enrichment.
Key Resources
See this content:
- "Accounts and Contacts" chapter in the Implementing Sales guide
- "Accounts, Contacts, and Households" chapter in the Using Sales guide
Use DataFox and D&B Together to Enrich Your Accounts
Enrich an account using Oracle DataFox and Oracle Account and Contact Enrichment by Dun & Bradstreet (D&B) simultaneously in real-time. You can use D&B to enrich some of the accounts fields and Oracle DataFox to enrich the others. But, for smart data, you need to use either DataFox or D&B.
You can use D&B and Oracle DataFox to enrich fields in Sales account records. For example, you can get the firmographic data, such as employee count and revenue, from D&B, and account scoring-related data from Oracle DataFox. This way, you can leverage Oracle DataFox capabilities for account scoring along with D&B firmographic data.
Steps to Enable
-
In the Setup and Maintenance work area, use the Manage Data Enrichment Integration task:
- Offering: Sales
- Functional Area: Integrations
- Task: Manage Data Enrichment Integration
- On the Manage Data Enrichment Integration page, select Enable DaaS and Enable DataFox for Enrichment.
- Select Enable DaaS for SmartData. (Don't select Enable DataFox for SmartData).
- Enter the credentials for DaaS and DataFox.
Mapping DataFox Fields
- Map the following three fields:
- DataFox Company ID
- Account Score
- Account Scoring Tier
- Remove the mapping for the other Oracle DataFox fields, because you can map only three Oracle DataFox fields for enrichment. See the Oracle DataFox documentation (https://docs.oracle.com/en/cloud/saas/datafox/dfudf/set-up-and-administer-oracle-cx-sales-integration.html) to learn more.
- Ensure that the Oracle Account and Contact Enrichment by Dun & Bradstreet (D&B) (formerly Oracle DaaS) mappings are correct, and map all the desired fields for DaaS except the three fields mapped for Oracle DataFox.
Tips And Considerations
In this release, Oracle has introduced a new task, Manage Data Enrichment Integration, to enable the coexistence of D&B and Oracle DataFox. Use the task to set up account enrichment.
Note: The following existing tasks that were used for enriching from Oracle DataFox and D&B are now deprecated:
- Manage DataFox Data Enrichment Integration
- Manage Integration with Oracle Data as a Service
These tasks will be removed after a couple of releases.
Key Resources
See this content:
Role Information
Sales Administrator
Dynamically Schedule Object Sharing Rules Processing for Access Group Rules
You no longer have to manually schedule the Perform Object Sharing Rule Assignment Processing job for each object to ensure access group object sharing rules are assigned at regular intervals. Provided an active rule exists for an object, the Perform Object Sharing Rule Assignment Processing process is dynamically scheduled to run for the object. How frequently the process runs varies depending on whether or not an object supports near real-time processing. You can disable dynamic scheduling, or change how frequently the process runs, using profile options.
Dynamic scheduling makes it easier for you to manage object sharing rules processing and improves rule processing performance.
Steps to Enable
The profile option, Dynamic Scheduling of Scheduled Process Jobs Enabled (ORA_MOW_ENABLE_ESSJOB_DYNAMIC_SCHEDULING), controls whether or not dynamic scheduling of object sharing rules processing is enabled. This option is enabled by default, but you can disable dynamic scheduling if necessary using these steps:
- Navigate to Setup and Maintenance.
- Open the Search page and search for the task Manage Administrator Profile Values.
- Search for the profile option Dynamic Scheduling of Scheduled Process Jobs Enabled.
- Change the default value of the profile option to No.
- Click Save and Close.
Tips And Considerations
You can specify how frequently the object sharing rules processing job runs when dynamic scheduling is enabled. These profile options let you specify the processing frequency when near real-time processing is enabled, and when near real-time processing is disabled:
- Frequency of Scheduled Process Jobs if Near Real-Time Processing Enabled (ORA_MOW_ESSJOB_FREQUENCY_WITHNRT): The default value is 6 hours.
- Frequency of Scheduled Process Jobs if Near Real-Time Processing Disabled (ORA_MOW_ESSJOB_FREQUENCY_WITHOUTNRT): The default value is 1 hour.
Key Resources
See the "Access Groups" chapter in the Securing CX Sales and B2B Service guide.
Role Information
Sales Administrator
Copy Object Sharing Rules from System and Custom Access Groups to Other Groups
You can easily copy all the predefined and custom object sharing rules assigned to an access group to other access groups. You can copy rules either to access groups you create, or to system access groups generated for custom job roles. You no longer have to manually assign rules to these types of access groups.
Creating custom access groups and implementing access groups generated for custom job roles is simplified. Instead of having to assign rules individually to these groups, you can copy the rules from an existing group that provides similar access to data as your custom group requires, and then publish only the copied rules relevant for your custom group.
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
For information on using Import and Export Management, see the Understanding Import and Export Management for CX Sales and B2B Service guide.
Track Import Job Completion Estimation
You can now track your import job completion estimation time. View the Manage Imports and Import Status pages to see the estimated time range within which an import job will be processed.
You can now know an estimated time range within which an import job will be processed, giving you better insights and predictability.
Steps to Enable
You don't need to do anything to enable this feature.
View and Save Only Your Export Maps
You can now save and view your export maps, in addition to keeping the maps private.
Use cases and benefits:
- During the export activity, there was significant rework while creating and accessing specific maps which you intended to reuse.
- Save your maps and, on subsequent use, access only your maps, thus speeding up your export job creation process.
- Mark maps as private, which will hide the maps from other users, thus personalizing your experience.
Steps to Enable
You don't need to do anything to enable this feature.
Use Do Call For Primary Contact Points in High Volume Import for Contact Object
You can use the Do Contact preference for primary work phone, primary mobile, primary home phone, primary email, and primary fax while importing contacts in Import Management.
These fields are available in Import Management under the Contact object for both standard and high-volume mode:
- DoCallMobilePhoneFlag
- DoCallWorkPhoneFlag
- DoCallHomePhoneFlag
- DoContactEmailFlag
- DoContactFaxFlag
In addition to the above, these fields are available in Export Management:
Contact object:
- MobilePhoneContactPtId
- WorkPhoneContactPtId
- HomePhoneContactPtId
- FaxContactPtId
- EmailContactPtId
Account object:
- PrimaryContactDoCallFlag
- PrimaryContactDoEmailFlag
Account Contact object (child of Account):
- DoCallFlag
- DoEmailFlag
The Contact preference information is important from compliance requirements. The Existing Phone and Email fields also provide Do Contact details. Contact point identifiers on the parent Contact object are helpful in integration use cases to easily map to child records in contact point child object for updates and fetch more information for that record.
Steps to Enable
You don't need to do anything to enable this feature.
Import and Export Access Extension Rules for Access Groups
Use Import and Export Management to import and export access extension rules in your sales environment. Access extension rules let you extend the access defined for an object in an object sharing rule to a related object. You can import access extension rules previously exported from the same or another environment, or can use this functionality to update multiple access extension rules at a time.
This feature lets you manage access extension rules more efficiently.
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
Sales Administrator
Use Do Call and Primary Phone Identifiers in Contact REST API Header
You can use the Do Contact preference and Contact Point identifier information at header level for primary work phone, primary mobile, primary home phone, primary email, and primary fax in the Contacts REST web service.
These fields are added to the Contact REST API:
Read-only:
- MobilePhoneContactPtId
- WorkPhoneContactPtId
- HomePhoneContactPtId
- FaxContactPtId
- EmailContactPtId
Editable:
- DoCallMobilePhoneFlag
- DoCallWorkPhoneFlag
- DoCallHomePhoneFlag
- DoContactEmailFlag
- DoContactFaxFlag
These fields are added to the Account REST API:
Read-only:
- PrimaryContactDoCallFlag
- PrimaryContactDoEmailFlag
These fields are added to the AccountContact child in the Account REST API:
Read-only:
- DoCallFlag
- DoEmailFlag
The contact preference information is important from compliance requirements. The existing Phone and Email fields will also provide Do Contact details. Contact point identifiers on parent Contact object are helpful in integration use cases to easily map to child records in contact point object for updates.
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.
Use Export REST APIs to Reuse a Saved Export Map
You can now use Export REST APIs to reuse a saved export map using a unique identifier.
This feature extends the reusability of the user-created Export Maps through the Export REST APIs. You can now pass a unique identifier as a parameter to refer to any previously created export map and not have to pass the entire filter expression, hence reducing opportunities for error or passing an erroneous expression.
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.
Use Simplified Setup for Duplicate Identification Options
Use the Manage Customer Data Management Options simplified setup page to review and configure the profile options used by duplicate identification. The new Duplicate Identification Options tab lets you configure the core duplicate identification profile options as a single configuration step. This new tab also provides on-page documentation and help to make it easy to choose the most appropriate options for your implementation.

Simplified Setup for Duplicate Identification Options
This enhancement simplifies the process for configuring profile options for Duplicate Identification by letting you configure multiple options as a single setup task and by making it easy to access the exact documentation sections needed to help your configuration decisions.
Steps to Enable
Here's how to access this enhancement:
- Navigate to Setup and Maintenance.
- Select the Customer Hub functional area in the Customer Data Management offering.
- Click on the link for the Manage Customer Data Management Options setup task.
- Navigate to the Duplicate Identification tab.
Tips And Considerations
It's still possible to review and configure Duplicate Identification profile options through other setup interfaces, but the Manage Customer Data Management Options interface provides a more efficient, tailored experience for the configuration process.
Key Resources
- See the "Duplicate Identification Setup" chapter in the Implementing Customer Data Management (CDM) for CX Sales and B2B Service guide.
Role Information
Users with the Master Data Management Application Administrator privilege can access the Manage Customer Data Management Options setup task.
Submit Resolution Request Dispatcher Jobs from the Duplicate Resolution Page
Submit the resolution request dispatcher jobs directly from the Duplicate Resolution page. Previously you had to go to the Run Request Dispatch Setup and Maintenance task to process resolution requests. Now you can click Dispatch on the Duplicate Resolution work area to set the status of pending resolution requests to new, as well as to send submitted resolution requests for processing.

Duplicate Resolution Page
The new Dispatch button on the Duplicate Resolution page lets data stewards to more efficiently advance the stage of in-progress resolution requests by running the request dispatch job without needing to leave the Duplicate Resolution page.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
The new Dispatch button creates the exact same Request Dispatcher job that's created through the Run Request Dispatch Job Setup and Maintenance task. The Run Request Dispatch Job will remain available in the Setup and Maintenance module and will continue to be used for configuring Request Dispatch job parameters, as well as for configuring any recurring execution schedules. Clicking the Dispatch button on the Duplicate Resolution page immediately submits a Request Dispatch job using the current default parameters, and users can monitor the status of the job using the Scheduled Tasks page in the exact same way that they would to monitor a job submitted from the Run Request Dispatch Job setup task page.
Key Resources
- See the "How You Merge Duplicate Records" section in the "Resolve Duplicates" chapter in the Using Customer Data Management for CX Sales and B2B Service guide.
Role Information
- Customer Data Steward
- Data Steward Manager
- Master Data Management Application Administrator
IMPORTANT Actions and Considerations
IMPACT OF NEW GROOVY VERSION ON EXISTING SCRIPTS AUTHORED IN APPLICATION COMPOSER
In this release, a new version of the Groovy scripting engine, version 2.5.14, is available with Application Composer. This new version changes some runtime application behavior, as described below. Review your existing Groovy to confirm that everything still operates as expected, or modify your scripts as needed.
1. LinkedList method behavior now matches Java behavior
The push and pop methods now work the same as in Java.
In Groovy 2.4.13 and below, LinkedList worked like a stack: Last In First Out (LIFO). In the new version, LinkedList works like a queue data structure: First In First Out (FIFO).
Let’s look at the push method:
| def LinkedList list=new LinkedList(); list.add('A'); list.add('B'); list.push('C'); list.add('D'); println(list); |
In 21D (Groovy 2.4.13 and below), the result was:
[A, B, C, D]
In 22A (Groovy 2.5.14), the result is now:
[C, A, B, D]
To preserve the same behavior of Groovy 2.4.x, modify your scripts as follows in Groovy 2.5.x:
Instead of list.push(), use list.add().
Next, let’s look at the pop method:
| def LinkedList list=new LinkedList(); list.add('A'); list.add('B'); list.add('C'); list.add('D'); println(list.pop()); |
In 21D (Groovy 2.4.13 and below), the result was:
prints "D"
In 22A (Groovy 2.5.14), the result is now:
prints "A"
To preserve the same behavior of Groovy 2.4.x, modify your scripts as follows in Groovy 2.5.x:
Replace list.pop() with def value = list.last() ; list.remove(value);
2. ObjectRange iterator now returns NoSuchElementException instead of null when hasNext returns false
Calling next() on an ObjectRange iterator now returns NoSuchElementException (instead of null) when hasNext returns false, to adhere to the Iterator contract.
| def itr = ('a'..'b').iterator() assert itr.next() == 'a'; assert itr.next() == 'b'; itr.next(); /* itr is null in 21D - in 22A it throws a NoSuchElementException) */ |
To preserve the same behavior of Groovy 2.4.x, modify your scripts as follows in Groovy 2.5.x:
To avoid getting the unchecked exception NoSuchElementException, always have itr.hasnext() check before calling itr.next.
BPM PROJECTS FOR OBJECT WORKFLOW APPROVAL FLOWS NOW STORED IN BPM 'FUSIONAPPS' SPACE
With the migration to Oracle Business Process Management (BPM) 12C, all projects deployed for use with Application Composer object workflows are now part of the "FusionApps" space in BPM. Users who created and deployed projects in previous releases automatically have access to this space in Update 22A. Users can access this space by creating a new project, editing an existing project, or by getting a list of all projects from Application Composer.
------------------------------------------------------------
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.
- Sign into the application.
- From the Navigator, select Sandboxes (under Configuration).
- Create a new sandbox and set it as the active sandbox. The current active sandbox displays at the top of the application.
- Go to: Navigator > Application Composer (under Configuration).
- From the Application drop-down list, select the first application whose metadata you want to upgrade, such as Common or Sales.
- 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.
- Click Metadata Upgrade.
- 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.
- 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.
- Repeat steps 7-8 for each row in the list.
- Repeat steps 4-8 for each application in the Application drop-down list in Application Composer.
- 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.