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

    Separate base and custom Restartable Error Messages

    Restartable Error Messages

    Small

    Yes

    No

    Enhanced auto-retry mechanism for restartable ReST Jobs

    Restartable Error Messages

    Small

    Yes

    No

    Extend expiry of IDCS JWT Tokens

    Authentication

    Small

    Yes

    No

Separate Base and Custom Restartable Error Messages for ReST Jobs

POM supports the definition of Restartable Error Messages through the Batch Schedule spreadsheet. It also allows customers to further customize these messages via the UI. When a job fails with one of these defined messages, POM automatically restarts it. In the current implementation, once a Restartable Error Message is customized through the UI, Oracle application teams can no longer modify it via the spreadsheet.

In 25.1.301.0, POM is introducing an enhancement where the base Restartable Error Messages from the spreadsheet are merged with the ones customized from the UI. This then allows Oracle product teams to modify these restartable messages. The merged value is reflected in the Job Agent popup when a new scheduler day is created and is also visible in job execution logs. This ensures both base and customer-defined messages are retained and used for automatic job restarts.

Enhanced Auto-retry Mechanism for Restartable ReST Jobs

Currently, POM automatically restarts ReST jobs that fail with Restartable Error Messages. After the initial failure, POM retries the job up to two more times each 30 seconds apart. POM has been enhanced to increase the number of retries to four. The retry logic has also been improved with the below incremental delays between attempts.

  • 1st retry: 30 seconds after the initial failure with a Restartable Error Message

  • 2nd retry: 40 seconds after the 2nd failure

  • 3rd retry: 50 seconds after the 3rd failure

  • 4th retry: 60 seconds after the 4th failure

Extend Expiry of IDCS JWT Tokens

POM integrates with various retail applications such as Merchandise Foundation Cloud Service (MFCS) and Retail Analytics and Planning (RAP), to name a few, as well as with customer applications. It uses a IDCS JWT token for authentication and authorization, when interacting with these applications. To reduce calls to IDCS, POM currently caches that token for an hour. To further improve the resiliency of integration flows, in this release, POM is extending the IDCS JWT token expiry from 1 hour to 8 hours. This change reduces the risk of authentication failures during IAM outages and minimizes rate-limit issues. This is done to ensure uninterrupted batch execution and reduction of business impact.