1. Release Readiness Guide
  2. Feature Summary

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.

    • 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.

Table 1-1 Noteworthy Enhancements

Feature Module Impacted Scale Delivered Customer Action Required?

API to Adjust Business Date

Integration

Small

Enabled

No

Added Logging Capability

Logging

Small

Enabled

No

Scheduler Enhancement

Scheduler

Small

Enabled

Possible

API to Adjust Business Date

In this version, POM provides a new API to adjust the business date of a Batch Schedule. This allows for aligning the business date with other schedules or a customer’s internal processing date. For example, if a customer uses their own scheduling mechanism to invoke batch runs in POM and they don’t want to process a batch on the weekend, they can invoke this API after the batch is complete on Friday to advance the POM business date to Monday.

Path

/ProcessServices/services/private/administration/utilities/alignBusinessDate

HTTP Method

POST

Request Payload

 
{
    "businessDate" : "2022-11-20",
    "scheduleName" : "RPASCE",
    "advanceDateOnly" : true, 
    "updateDependentSchedules" : true,
    "comment": "To run schedule for 20-NOV-2022"
}

The advanceDateOnly flag ensures that the business dates are being moved forward and not backwards. If any of the Schedules need to be adjusted to an older date, it will cause the request to fail. This is an optional flag that defaults to false.

The updateDependentSchedules flag ensures that all the dependent schedules are adjusted to the same business date, along with the primary schedule. This is an optional flag that defaults to false.

Authentication

Authorization = Basic <Base64 Encoded Credentials>

For the full API specification, see the “Business Date Alignment” section of the Integration chapter in the Process Orchestration and Monitoring 19.1 Implementation Guide.

Added Logging Capability

POM previously lacked an audit trail for actions such as disabling the Scheduler, restarting the Schedule for the day, and so on.

In this version of POM, logging capabilities have been added for most actions performed on the UI and through APIs.

At this point, the logs containing these audit trails are only accessible by the Oracle AMS team. Customers need to contact Oracle support for inquiries related to the audit trail. In future versions, this audit trail will be accessible to customer administrators through the UI.

Scheduler Enhancement

In previous versions, POM omitted scheduling tasks if the Scheduler was disabled. In this version, POM has enhanced its Scheduler feature to schedule enabled tasks when a New Scheduler Day is created, even if the Scheduler is disabled for a given Batch Schedule. This ensures that enabled tasks are scheduled regardless of the Scheduler state, just in case someone has disabled the Scheduler temporarily and intendeds to enable it later.

Because of this change, actions by customers may be required depending on whether or not they use the POM Scheduler feature to schedule when jobs run.

If a customer does not use the POM Scheduler and therefore has it permanently disabled, then if there are Scheduler Tasks enabled on the Scheduler Administration screen, failure notifications will be generated for the SchedulerTaskFailed notification type when POM attempts to execute those tasks. The customer will even receive email notifications for those tasks if they have subscribed to receive those emails on the Manage Notifications feature of Retail Home. In previous versions, POM did not schedule those tasks when the Scheduler was disabled (as mentioned above) and thus this was not an issue. It is therefore recommended in this case to disable the individual scheduler tasks using the Scheduler Administration screen to prevent those notifications from being generated.