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
IDCS Scope Restriction Readiness – Steps for External Integrations	Web Services	Small	No	Yes

IDCS Scope Restriction Readiness – Steps for External Integrations

IDCS or OCI IAM has announced restricting the use of urn:opc:idm:__myscopes__ which will require individual services to have their own predefined scopes.

REST and SOAP services exposed externally by Order Broker require authentication from IDCS or OCI IAM, which is obtained by providing the IDCS OAuth Client ID and Secret along with a scope. In most cases, unless a service has a predefined scope, the scope urn:opc:idm:__myscopes__ is used. This scope grants broad access to all scopes associated with the specified OAUTH Client ID.

Because there are no predefined scopes in Order Broker, a new scope will need to be created to address this change. This will be a one-time setup performed by Oracle, with the new scope being assigned to the relevant OAuth Clients via Retail Home. To have a scope created and assigned to clients, submit a Service Request on My Oracle Support.  

Customers currently using urn:opc:idm:__myscopes__ are advised to switch to the new scope to avoid potential disruption. This advisory encourages customers to make this change proactively, ahead of the planned updates from IDCS or OCI IAM, to minimize any impact.