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? |
|---|---|---|---|---|
|
Cards/Program |
Small |
Enabled with Card/Program functionality |
No |
|
|
Promotion |
Small |
Enabled with the Promotion functionality |
No |
|
|
Classic View User Interface |
Small |
Automatically Removed |
No |
|
|
New Product |
Medium |
With License Purchase |
Yes |
New Feature Description
This section describes the new features.
Program Enhancements
Tooltips are added to the Tender, Award, and Loyalty program scorecards for Redemption Rate, Customer in Program, Registered Accounts, and Average Balance per Account so that the calculation is available in the user interface.
A disclaimer is added to the Program Scorecard that will call out when the data was compiled with the aggregated job name and run date/time.
The full card number will be displayed in the Customer Engagement user interface.
The Tender Program Active Account graph date is updated to be consistent with the Loyalty and Award. The date will now be displayed in Month and Year format, three-character month and four-digit year (for example, Mar 2022 and Apr 2020).
Performance enhancements are added to the Card Search that allow for quicker results while performing partial match searches.
Promotion Setup Enhancements
The End Date for promotion setup is changed to default the ending time to 11:59 pm and not 12:00 am. Also, the date and time have been split into separate fields, so there are now Start Date, Start Time, End Date, and End Time fields.
Performance enhancements are added to the Promotion Setup Wizard to improve response times on the Program, Audience, and Review tabs. Spinners are added to the UI that will show data is being populated in the Promotion Scorecard.
Classic View
Access to the Classic View has been removed from the Customer Engagement user interface. For additional information on setting up home roles for user login, see theOracle Retail Customer Engagement Implementation Guide.
Retail Data Store (RDS) Availability
Oracle Retail Data Store enables retailers to unlock the value of their data through a comprehensive set of tools, enabling virtually unlimited extensibility while abstracting those workloads from those of the original Oracle Retail cloud services. This toolset allows the retailer to create a wide variety of functionality that they can tailor specifically to their own business processes. Examples include custom web services to expose specific data elements, custom integration (inbound and outbound), reporting and analytics, and custom user interfaces for capture retailer-specific data.
A separate subscription different from Customer Engagement Cloud Service is required for Oracle Retail Data Store, which is composed of two parts:
-
Oracle Retail Data Compute Cloud Service – this portion of the subscription covers compute resources available to the cloud service and allows a retailer to add compute to their solution as necessary for their extensions.
-
Oracle Retail Data Storage Cloud Service – this portion of the subscription covers data storage resources available to the cloud service and allows a retailer to add storage to their solution as necessary for these extensions.
For more information about RDS, see its documentation set on the Oracle Help Center.