1 Feature Summary
This section describes the feature enhancements in this release.
Supported Retail Integration Products
The Oracle Retail Integration Cloud Service (RICS) is composed of the Oracle Retail Integration Suite of products that are cloud deployable for a customer's integration to Oracle Retail applications and the customer's on-premises or hybrid configurations of third-party applications.
The integration products supported and mentioned in this document are the same as the generally available on-premises versions of the following applications:
-
Oracle Retail Integration Bus (RIB)
-
Oracle Retail Bulk Data Integration (BDI)
-
Retail Financial Integration (RFI)
-
Universal service Mapper (USM).
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.
Feature Module Impacted Scale Delivered Customer Action Required? New and Updated Options RIB, BDI, USM, TOOLS, RFI
Small
Y
N
Infrastructure and Security Compliance
RIB, BDI, USM, TOOLS, RFI
Large
Y
N
Documentation
RIB, BDI, USM, Tools, RFI
N/A
Y
N
New and Updated Options
Use Service Principal and RPST for IDCS Calls
The creation of IDCS user groups and updates to the web tier policy now takes place through calls to the identity service’s REST APIs using service principals. The REST services are hosted as idp-jobs and authorized using RPST. Identity blocks clientid/secret generated bearer token authentication and is thus not valid anymore. Identity has allowlisted the service principals to be able to invoke these APIs using Resource Principal Session Token (RPST).