1 Feature Summary
The following enhancements are included in this release.
Noteworthy Enhancements
This guide outlines the information you need to know about new or improved functionality in the Oracle Retail Home 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.
-
Delivered: Identifies whether the feature is Enabled or Disabled upon initial delivery.
-
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.
-
- 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? |
|---|---|---|---|---|
|
Oracle Digital Assistant |
Medium |
Yes |
No |
|
|
OAuth Client Creation for Xstore Office On-Prem to AIFNDCS Integration |
Manage OAuth Clients |
Small |
Yes |
No |
|
OAuth Client Creation for Xstore Office On-Prem to RH/PSRAF Integration |
Manage OAuth Clients |
Small |
Yes |
No |
Oracle Digital Assistant (ODA) Integration in Retail Home
Retail Home is integrated with the Oracle Digital Assistant. The Oracle Digital Assistant (ODA) is an AI-powered platform that enables users to interact with various business applications and services through natural conversations via chat interfaces. ODA is being used to bring together information, workflows, and assistance from multiple documentation sources into a single, unified experience.
With ODA, end users can get the following and more:
- Answers Quickly: Ask questions and receive timely, accurate responses to common queries about applications, policies, or business processes.
- Personalized Experience: Receive tailored information and notifications based on your role, preferences, and recent activity.
- Simple Interaction: Use natural language (typing or speaking) to communicate. ODA is designed to understand common phrases and conversational requests.
For the best experience, access the ODA window by clicking the conversation icon at the bottom of the screen, state your request or question clearly, and follow prompts or suggestions as they appear. If ODA cannot resolve your request, consult the documentation or log a service request to get additional support.
If there is an issue accessing ODA, customers are advised to log a service request (SR), so that Oracle can provide a resolution.
OAuth Client Creation for Xstore Office On-Prem to AIFNDCS Integration
Retail Home is now enhanced to allow retailers to create a dedicated OAuth Client for Xstore Office On-Prem to AIFNDCS integration. A new template, such as Xoffice OnPrem AIFNDCS App, is introduced with a locked-down app name format (for example, RGBU_XTROFFOP_ENV_XOFFICE_AIFNDCS, where ENV represents the environment like PRD1 or STG1) and applicable AIF-specific scopes (for example, rgbu:rsp:RSP-PRD1). The app is also granted the Application Administrator IDCS AppRole to support the creation of additional OAuth clients required by Xstore components.
OAuth Client Creation for Xstore Office On-Prem to RH/PSRAF Integration
Retail Home is now enhanced to allow retailers to create a dedicated OAuth Client for Xstore Office On-Prem to RH/PSRAF integration. A new template, such as Xoffice OnPrem RH App is introduced with a locked-down app name format (for example, RGBU_XTROFFOP_ENV_XOFFICE_RH, where ENV represents the RH environment like PRD1 or STG1) and applicable RH-specific scopes (for example, rgbu:RH:services-PRD1). The app is granted the User Viewer IDCS AppRole to support RH API access. Upon creation, the client ID, client secret, and scope are displayed for user reference.