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.

    • 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 Public APIs

Public APIs

Small

Yes

No
Private APIs Made Public

Public APIs

Small

Yes

Yes, if private API is used

Long Run Tolerance

Job Execution

Small

Yes

No

New Public APIs

The following new APIs were added to allow retailers to better integrate their internal systems with POM:

  • Get Job Instances - services/public/schedules/{{SCHEDULE_NAME}}/jobInstances?cycle={{cycleName}}

  • Rerun Job - services/public/schedules/{{SCHEDULE_NAME}}/jobInstances/{{jobRunId}}/run

  • Skip Job - services/public/schedules/{{SCHEDULE_NAME}}/jobInstances/{{jobRunId}}/skip

  • Kill Job - services/public/schedules/{{SCHEDULE_NAME}}/jobInstances/{{jobRunId}}/kill

  • Download Cycle summary - services/public/schedules/{{SCHEDULE_NAME}}/jobInstances/summary

  • Download Job Log - services/public/schedules/{{SCHEDULE_NAME}}/jobInstances/{{jobRunId}}/executions/{{executionId}}/log

  • Create Execution Request - services/public/schedules/{{SCHEDULE_NAME}}/executionRequests

Private APIs Made Public

Before this release, POM exposed the Execution Request Creation API as a private API as follows:

https://<pom-server-host>/ProcessServices/services/private/excecutionEngine/schedules/<schedule-name>/execution

Oracle reserves the right to change its private APIs anytime without notice. To avoid impact to customers, the public version of this API is provided with this release. The use of the private version is discouraged.

If a retailer is currently using the above private API, they are advised to switch to using this new public version as soon as possible.

https://<pom-server-host>/ProcessServices/services/public/schedules/<schedules/<schedule-name>/executionRequests.

Long Run Tolerance

A Long Run Tolerance was added to the suite of levers for determining whether a job is long-running. This configurable tolerance pads a job’s calculated long-running threshold. It’s meant to help reduce the number of long-running notifications, especially for short-running jobs.

This new tolerance will not be used in the cases where a job has a Threshold Run Time set (on the Batch Administration screen), nor if the job has no Threshold Run Time set and has no history. In the latter case, the existing system’s defaultLongRunningThresholdRunTime (defined as a system option on the System Configuration screen) is used as the threshold. This new tolerance is only used for padding in the case where we use the job's average run time * long run average time multiplier (defined on the System Configuration screen).


So, a long-run notification is generated in the following cases:

  • A job has a Threshold Run Time set and the job's run time exceeds that.

  • A job has no Threshold Run Time set, no history, and the job's run time exceeds the existing system’s defaultLongRunningThresholdRunTime.

  • A job has history and no Threshold Run Time set. In this case the calculated threshold is X = average runtime * long run average time multiplier. If the job's runtime exceeds X + the new Long Run Tolerance, then a notification is generated.

The default value for Long Run Tolerance is 360 seconds. To update this value for a particular schedule, the value of the system option defaultLongRunningToleranceLevel needs to be updated on the System Configuration screen.