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? |
|---|---|---|---|---|
| Synonym Creation |
All Workspaces |
Small |
Yes |
Yes |
| DBMS_ALERT |
All Workspaces |
Small |
Yes |
No |
| Session Management |
RDS Database Ops Console |
Small |
Yes |
No |
| Optimizer Stats Collection |
All Workspaces |
Small |
Yes |
No |
Synonym Creation
Synonym creation is now self-service, giving you greater flexibility in naming custom database objects. Without synonyms, you reference replicated objects using a fully qualified name (for example, MFCS_RDS.RDS_WV_ITEM_MASTER). When you run the synonym creation process, any name collisions between replicated object synonyms and your custom objects trigger a warning, but the process continues. If you choose to use the default synonym name of a replicated object for a custom object, you can still access the replicated object using its fully qualified name, or by creating your own synonym for it.
Synonym behavior depends on environment provisioning:
-
Existing RDS environments retain all previously created synonyms.
-
Newly provisioned RDS environments do not include any synonyms by default.
To add synonyms to new environments or update existing ones as cloud services evolve, use the synonym creation API
.DBMS ALERT
The DBMS_ALERT package is now available for use. This package allows asynchronous communication between sessions within the database. You can use it to signal and wait for events, which is especially useful for coordinating actions across different sessions or processes without constant polling.
Session Management
Session Management in the RDS Database Operations Console now includes visibility into additional sessions associated with APEX application execution and APEX UI operations. This enhancement provides more comprehensive monitoring and troubleshooting capabilities for APEX-related activity.