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 Process Orchestration and Monitoring 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 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
    Self-Service Data Refresh for RAP Customers Data Migration Medium Yes Yes
    OAUTH2 Authentication for POM Callbacks External Status Update Small Yes Yes, if a change from Basic Auth to OAuth is desired for Callbacks
    Prevent Nightly Cycle from Starting During Ad Hoc Execution Batch Execution Small Yes No
    Accept Full URL for External Authentication Custom Jobs Small Yes No

Self Service Data Refresh for RAP Customers

A new data migration feature has been introduced in POM to allow Oracle and customers to refresh data from one environment to another. This feature has been developed incrementally and is currently only available to the Retail Analytics and Planning (RAP) customers. An administrative user can request an ADW Clone be performed from one environment to another, (for example, production to stage). A new data migration menu item has been introduced in POM for that purpose.

To access this new feature, two new POM application groups/roles have been introduced. The 25.1.201.0 POM update seeds these two new roles and their PREPROD counterparts in the customers Identity Domain. If you, as a customer, do not want these two new roles seeded, notify the Customer Success Manager to inform the Oracle Operations team before the 25.1.201.0 update is applied.

After the update, customers must assign users to these groups to grant them access to this new feature.

Role Privileges
DM_ADMINISTRATOR_JOB Retailer administrators who can perform all actions on the Data Migration Configuration and Operations screens.
DM_MONITOR_JOB Retailer users who can only view and restart data migrations that are in progress. Users in this role cannot initiate new migrations.

Note:

In this release, POM only supports cloning when the source and destination environments are running the same application version. Removing this restriction is being considered, if technically feasible.

Also note that in this release, POM does not support cloning of integrated environments where GoldenGate is enabled.

OAUTH2 Authentication for POM Callbacks

The External Status Update feature in POM allows external systems to optionally register with POM to receive job status notifications via a callback to their ReST interface. Previously, POM supported external callbacks using only BASIC authentication. This enhancement introduces support for OAuth-based external callbacks.

The External Configuration panel of the System Configuration screen was modified to allow entry of OAuth specific information.

Prevent Nightly Cycle from Starting During Ad Hoc Execution

A new flag has been introduced to prevent the Nightly cycle from starting if a specific ad hoc job is currently running. The flag can be enabled from Scheduler Administration screen for the corresponding Scheduler Task. Nightly is delayed until the job has completed successfully. This flag also prevents the adhoc job from starting when the Nightly Cycle is running.

Accept Full URL for External Authentication

As part of its customization capabilities, POM allows for the creation of custom job types for use with custom jobs. When defining custom job types on the System Configuration screen, customers can use a non-default (custom) IDCS slice for authenticating custom job ReST calls. Currently, POM automatically appends /oauth2/v1/token to any URL entered for the custom IDCS slice. An enhancement has been implemented allowing POM to accept a full URL, thus allowing the use of an external authentication service if needed. The customer can still specify an internal IDCS URL and let POM append /oauth2/v1/token.