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 Features
    Identity and Access Management Changes

    Access Management

    Large

    Yes

    Yes – Before July 2027
    Move Email Notifications from System Level to Batch Schedule Level

    Notifications

    Medium

    Yes

    Yes – If making changes to email notifications configuration
    Long Run Notification Improvements

    Notifications

    Small

    Yes

    No
    UI Performance Improvements

    User Interface

    Small

    Yes

    No
    Enhanced Callback Payload

    External Status Update (Callback)

    Small

    Yes

    No
    Enable Callback for Manually Run Jobs

    External Status Update (Callback)

    Small

    Yes

    No
    Enhanced Schedules Public API

    POM Integration

    Small

    Yes

    No
    Integration with Oracle Digital Assistant

    Artificial Intelligence

    Small

    Yes

    No
    AI-assisted Batch Error Resolution

    Artificial Intelligence

    Small

    Yes

    No

Identity and Access Management Changes

POM is introducing the following identity and access management changes in v26.2.301.0

Use of Oracle Internal IDCS

In order to support Oracle operational access to customer environments, and to provide a more robust service, POM will be routing Oracle operations users and POM internal flows through an internal Oracle Retail IDCS instance.

This also ensures that Oracle no longer requires access to a customer IAM identity domain, nor any Oracle users created within customer’s IAM identity domain.

Access by Oracle users will be highly restricted to Oracle operations personnel. Customers will also be able to review tracked activities performed by those users. This ability will be available in the Retail Home application in a future release. Until then, customers can request access logs from Oracle support.

Migration to Application Roles

In previous versions, POM automatically seeded the following IDCS Groups as part of provisioning:

  • PLATFORM_SERVICES_ADMINISTRATOR_ABSTRACT

  • PLATFORM_SERVICES_ADMINISTRATOR_ABSTRACT_PREPROD

  • PLATFORM_SERVICES_ADMINISTRATOR

  • PLATFORM_SERVICES_ADMINISTRATOR_PREPROD

  • DATA_PRIVACY_ADMINISTRATOR_JOB

  • DATA_PRIVACY_ADMINISTRATOR_JOB_PREPROD

  • DATAPRIV_ADMINISTRATOR_REST_API_ROLE

  • DATAPRIV_ADMINISTRATOR_REST_API_ROLE_PREPROD

  • BATCH_VIEWER_JOB

  • BATCH_VIEWER_JOB_PREPROD

  • BATCH_SCHEDULE_ADMINISTRATOR_JOB

  • BATCH_SCHEDULE_ADMINISTRATOR_JOB_PREPROD

  • BATCH_SCHEDULE_CONFIGURATION_MANAGER_JOB

  • BATCH_SCHEDULE_CONFIGURATION_MANAGER_JOB_PREPROD

  • BATCH_ADMINISTRATOR_JOB

  • BATCH_ADMINISTRATOR_JOB_PREPROD

  • BATCH_ORACLE_AMS_ADMINISTRATOR_JOB

  • BATCH_ORACLE_AMS_ADMINISTRATOR_JOB_PREPROD

  • DM_ADMINISTRATOR_JOB

  • DM_ADMINISTRATOR_JOB_PREPROD

  • DM_MONITOR_JOB

  • DM_MONITOR_JOB_PREPROD

However, from v26.2.301.0 onwards, POM will no longer seed these IDCS Groups for newly provisioned environments.

To align with industry standards and to standardize identity management across Retail applications, POM is moving to an application roles model.

POM will be seeding the following application roles into customers IDCS. Notice that these application roles are named the same as the above groups:

  • PLATFORM_SERVICES_ADMINISTRATOR_ABSTRACT

  • PLATFORM_SERVICES_ADMINISTRATOR

  • DATA_PRIVACY_ADMINISTRATOR_JOB

  • BATCH_VIEWER_JOB

  • BATCH_SCHEDULE_ADMINISTRATOR_JOB

  • BATCH_SCHEDULE_CONFIGURATION_MANAGER_JOB

  • BATCH_ADMINISTRATOR_JOB

  • DM_ADMINISTRATOR_JOB

  • DM_MONITOR_JOB

For access management, customers must perform the following steps:

New Environments

For new environments, this new application role model will be enabled by default. Customers are required to perform the following tasks in those new environments:

  • Create their own IDCS groups as per their preference. They have the option to keep the same existing group names if they would like

  • Map those groups to the above-mentioned POM application roles

  • Assign users to the customers’ IDCS groups created above.

Existing Environments

For existing environments, customers can retain their current setup and migrate with minimal impact by reusing the previously seeded POM groups.

To move to the new model for existing environments, customers must perform the following steps:

  • Retain the existing POM seeded IDCS groups.

  • Map the existing groups to the new POM application roles.

  • Verify that users who are assigned to the existing groups now have the same required access.

  • Continue maintaining those IDCS groups as customer managed groups going forward.

Oracle recommends that existing customers migrate to this model at the earliest opportunity. The existing group based model is being deprecated and will continue to be supported only until the July 2027 POM release (27.2.301.0). Customers therefore have one year to complete migration to the new application role model.

Move Email Notifications from System Level to Batch Schedule Level

In previous versions, the email configuration for Notifications was specified at a System level. This meant that if an email recipient subscribed to a specific notification, they would receive email notifications for all batch schedules within that POM instance. This became an issue with the introduction of custom schedules, as Oracle internal recipients would not receive notifications for those custom schedules.

In version 26.2.301.0, POM has moved all email configuration for Notifications from the System level to the individual batch schedules level. This enables Oracle operations to remove Oracle distribution lists from the custom schedules, which they do not monitor.

Although subscribing to notifications at the System level is still possible, customers are discouraged from this practice and are strongly recommended to subscribe to notifications at the individual schedule level.

Long Run Notification Improvements

In version 26.2.301.0, POM added two long run notifications improvements:

  • Option to only receive long run notifications if a job’s long run will potentially cause the Nightly target batch duration to be surpassed. To take advantage of this option, a customer needs to make sure the Target Batch Duration is set to a reasonable time period on the Settings window of the particular schedule on the System Configuration screen. Currently this defaults to 150 minutes. The customer also needs to enable the Nightly Batch Window Long Running Alerts flag on that same window.

  • Ability to turn off long run notifications for non-nightly jobs (Adhoc and Hourly). Before this version, the user received long running notifications for jobs of all cycles (Nightly, Adhoc and Hourly). As of 26.2.301.0, if the user elects to only receive notifications when the Nightly target batch duration is surpassed, the user might also want to elect not to receive Adhoc and Hourly long run notifications. To make that election, disable Manual Run Callback on the Settings window of the particular schedule on the System Configuration screen.

UI Performance Improvements

In version 26.2.301.0, POM made the following UI performance improvements:

  • Removed the job count for all cycles from the Schedule tiles at the top of both Batch Administration and Scheduler Administration screens. This saves screen loading time. The job counts can still be seen on each cycle tab right below the tiles.

  • Perform loading activities in parallel on Batch Monitoring screen.

  • On initial load of POM, load all necessary libraries in parallel.

  • Added a spinner on the Batch Monitoring screen so the user is aware the screen is making progress loading and is not stuck.

Enhanced Callback Payload

In version 26.2.301.0, POM has added the following fields to the External Status Update (Callback) payload:

  • jobStartTime

  • jobEndTime

  • jobExecutionDuration

  • jobLongRunningInd

  • activityProcessName

  • requestType

Enable Callback for Manually Run Jobs

In previous versions, POM would not send External Status Updates (Callbacks) for manually run jobs (from the UI). In version 26.2.301.0, POM provides an option - Manual Run Callback - on the Settings window of a particular schedule on the System Configuration screen. It is disabled by default, but when enabled, POM will send callbacks for manually run jobs.

Enhanced Schedules Public API

In version 26.2.301.0, the public API - ProcessServices/services/public/schedules – has been enhanced to include the following fields. These fields provide visibility of the Scheduler and Execution Engine status.

  • schedulerEnabled

  • executionEngineEnabled

Integration with Oracle Digital Assistant

In version 26.2.301.0, POM is introducing the POM Assistant, an AI-powered assistant integrated with Oracle Digital Assistant. The assistant is designed to help users find information and answer questions about POM using the User Guide, Implementation Guide, and Oracle’s internal POM support knowledge base. The POM Assistant can be accessed by clicking the POM Assistant icon located in the bottom-right corner of the application.

AI-assisted Batch Error Resolution

In version 26.2.301.0, POM is introducing the Analyze Error feature for failed batch jobs. Accessible from the Batch Monitoring screen by clicking the job status hyperlink of a failed job, this feature provides an AI-generated analysis that includes a summary of the error, possible root causes, and recommended actions to help users diagnose and resolve issues more quickly.