1 Feature Summary
This chapter describes the feature enhancements in this release.
Noteworthy Enhancements
This guide outlines the information you need to know about new or improved functionality in the Oracle Retail Customer Engagement (ORCE) update and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.
Column Definitions
-
Feature: Provides a description of the feature being delivered.
-
Module Impacted: Identifies the module associated with the feature, if any.
-
Scale: Identifies the size of the feature. Options are:
-
Small: These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
-
Large: These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
-
-
Delivered: Is the new feature available for use immediately after upgrade or must the feature be enabled or configured? If no, the feature is non-disruptive to end users and action is required (detailed steps below) to make the feature ready to use.
- Customer Action Required: You must take action before these features can be used. These features are delivered disabled and you choose if and when to enable them.
Table 1-1 Noteworthy Enhancements
| Feature | Module Impacted | Scale | Delivered | Customer Action Required? |
|---|---|---|---|---|
|
Data Movement |
Large |
Yes |
No |
|
|
Data Movement |
Large |
Yes |
No |
|
|
Reports |
Large |
Yes |
No |
New Feature Description
This section describes the new features.
Object Storage
Replacement for sFTP starting in ORCE release 20.0. The user will need to send a REST call to ORCE to get a Pre-Authenticated Request (PAR) that will be used to send files to Object Storage via scripting or some other process. This impacts sending and retrieving files in ORCE.
For more information on this function, see the Oracle Retail Customer Engagement Cloud Service Implementation Playbook. The guide is available on My Oracle Support in the Oracle Retail Customer Engagement Cloud Service Documentation Library MOS Doc ID 1994453.1.
Batch Files
Batch files should be pushed to object storage in .zip format.
For more details, see the Oracle Retail Customer Engagement Cloud Service Implementation Playbook. The guide is available on My Oracle Support in the Oracle Retail Customer Engagement Cloud Service Documentation Library MOS Doc ID 1994453.1.
BI Publisher
There is now one BI Publisher server for all Oracle products utilized.
For more details, see the Oracle Retail Customer Engagement Cloud Service Implementation Playbook. The guide is available on My Oracle Support in the Oracle Retail Customer Engagement Cloud Service Documentation Library MOS Doc ID 1994453.1.