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? |
|---|---|---|---|---|
| Auxiliary Workspaces |
RDS |
Small |
Yes |
No |
| Session Management API |
RDS |
Small |
Yes |
No |
Auxiliary Workspaces
Retail Data Store (RDS) now includes three additional workspaces that can be used in any manner the customer chooses. They can be used to segment code, sandbox code, or refine access control. They can be used in both development and production. The customer must grant access to any custom database object or Oracle Database objects (for example, MFCS_RDS_CUSTOM views) before they can be used in these workspaces.
Session Management API
A small Session Management API is now provided. This API allows the user to list custom Database Sessions and terminate any custom sessions the user deems problematic. The API addresses a situation where several rogue, runaway, or zombie sessions have accumulated and terminating such sessions from the Database Operations Console would be burdensome. The customer is still responsible for identifying which sessions are appropriate candidates for termination.
A Plan to Change Synonym Creation
Please note that Oracle Retail development is planning to change the creation of synonyms for replicated views in the custom schemas in RDS from an automated process to an on-demand self-service process. The design is that a PL/SQL API will be made available allowing customers create synonyms in their custom schema only when and if they want to do so.