1 Feature Summary
Noteworthy Enhancements
This guide outlines the information you need to know about new or improved functionality in the Oracle Retail Order Broker Cloud Service 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.
| Feature | Module Impacted | Scale | Delivered | Customer Action Required? |
|---|---|---|---|---|
| New and Updated Options | ||||
|
Order Broker |
Medium |
Yes |
Yes |
|
|
Order Broker – Vendor Portal |
Medium |
Yes |
Yes |
|
|
Order Broker – Store Connect |
Medium |
Yes |
Yes |
|
External Application Client Management
With this update, the Manage External Application Access screen now calls Oracle Retail Home APIs, instead of IDCS (Oracle Identity Cloud Service) or OCI IAM (Oracle Cloud Infrastructure Identity and Access Management) APIs, to generate new application clients and secrets, and to regenerate a secret for an existing client. This enhancement streamlines the client management process and improves security by centralizing client-related operations.
Two new properties, available in the Tenant-Admin screen, are introduced to facilitate Retail Home API integration:
-
Retail Home Service URL: Stores the URL of the Retail Home service, auto-populated during the upgrade.
-
Retail Home Scope: Defines the scope for the Retail Home service, also auto-populated.
Note:
Oracle Retail Home version 25.1.301.0 or above is required.
Order Broker will continue to communicate directly to IDCS or OCI IAM for retrieving new clients and new user creation.
The ability to generate an ‘Xoffice On Prem’ client is no longer available within Order Broker. Instead, within the Manage OAuth Client option in Retail Home, create the Client using the ‘Xoffice OnPrem Omni App’ template, if not already created. Once created in Retail Home, click Refresh Applications to update the clients and assign web service access.
Vendor User Group Management
With this update, the Identity Cloud User Synchronization job no longer automatically creates the vendor user groups in IDCS or OCI IAM that corresponded to each vendor created in Order Broker.
Previously created vendor user groups will still be available in IDCS or OCI IAM. For new vendors, the vendor user groups will need to be manually created in IDCS or OCI IAM. The group should be created as ‘<system>|<vendor>’, where:
-
<system> is the system code identifying the default vendor system.
-
<vendor> is the code identifying the vendor.
The vendor user group should then be assigned to the OBCS_Vendor_User role in IDCS or OCI IAM.
Store Connect User Group Management
With this update, the Identity Cloud User Synchronization job no longer automatically creates the Store Connect user groups in IDCS or OCI IAM that correspond to each Store Connect system created in Order Broker.
Previously created Store Connect user groups will still be available in IDCS or OCI IAM. For new Store Connect systems, the store connect user groups will need to be manually created in IDCS or OCI IAM. The group should be created as ‘STC-<system>’, where <system> is the system code identifying the default Store Connect system.
The Store Connect user group should then be assigned to the OBCS_Store_User role in IDCS or OCI IAM.