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 Data Store 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 impacted 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.
-
Medium: These UI or process-based features are typically comprised of field, validation, or program changes. Therefore, the potential impact to users is moderate.
-
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.
Scheduled Noteworthy Enhancements for Retail Data Store (RDS)
| Feature | Module Impacted | Scale | Delivered | Customer Action Required? |
|---|---|---|---|---|
|
Replicated Data |
Small |
Yes |
No |
|
|
ORCE, RMFCS, OROB, XOCS, SIOCS, SE, BC, OMS, RICS |
Small |
Yes |
No |
|
|
Consult product team and documentation |
Medium |
Consult product team and documentation |
No |
|
|
ORCE, RMFCS, OROB, XOCS, SIOCS, SE, BC, OMS, RICS |
Small |
Yes |
No |
|
|
ORCE, RMFCS, OROB, XOCS, SIOCS, SE, BC, OMS, RICS |
Small |
Yes |
No |
|
|
ORCE, RMFCS, OROB, XOCS, SIOCS, SE, BC, OMS, RICS |
Small |
Yes |
Yes |
New and Updated Options for RDS
Automatic Purge of Audit/Delete Tables
Data in audit/delete tables is now retained for 12 months. Data is purged monthly. If you wish to retain the audit/delete data longer than the standard retention period, you will need to copy the audit/delete data into a custom schema (e.g., MFCS_RDS_CUSTOM).
APEX System Patch Notification
You will be notified when APEX patches will be applied to your environments. The notification will be displayed on the workspace login page as well as on the APEX UI home page. Be aware, during the patch process, the ADW instance will be unreachable through any service, the APEX UI will be unavailable, and APEX apps and service calls will be interrupted. It is recommended that APEX interaction be suspended during the patch period.
Multi-Schema Support
RDS now supports multiple schemas per product. Not all products, however, support or require multiple schemas. Consult the relevant product team and documentation for additional details on product multi-schema support.
Kill Session
You are now able to kill rogue or run-away sessions at your discretion from the Retail DB Ops Console. The console provides the details necessary to identify potentially problematic sessions running your code. Note that you must still make the determination as whether the session has gone rogue or is host to a well behaved but long running process. The console cannot make this determination for you.
Data Visualizer and BI Publisher Connection Types
You can now select data connections when creating a dataset (Data Visualizer) or data model (BI Publisher) that is mapped to HIGH, MEDIUM, and LOW resource consumer groups. Familiarize yourself with the pros and cons of selecting one connection type over another. Also remember that RDS does not auto-scale. If your report consumes more resources, there will be fewer or no resources available to others.
Private Endpoint Database Access
The Oracle Retail Data Store (RDS) is accessible through the APEX Developer Environment as well as through custom APEX applications and services developed by the customer. Private endpoints extend access to RDS within your virtual cloud network (VCN) on Oracle Cloud Infrastructure or to other networks peered to the VCN such as your corporate network. That is, you can access RDS from hosts within your VCN or from your on-premises network.
When you set up a private endpoint for RDS, the Virtual Network Interface Card (VNIC) is set up for you, and its availability is maintained on your behalf. Your only responsibility is to maintain the subnet and the security rules.