1 Feature Summary
Oracle Retail Process Orchestration and Monitoring 24.1.401.0 is a Critical Update.
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? |
|---|---|---|---|---|
| Ability to Restart Failed Bulk Data Interface (BDI) Jobs from Process Orchestration and Monitoring |
BDI Jobs |
Small |
Yes |
No |
| Change in Format of Notification Tab in Exported Spreadsheet |
Export/Import |
Small |
Yes |
No |
Ability to Restart Failed Bulk Data Interface (BDI) Jobs from Process Orchestration and Monitoring
Previously upon failure, the user had to go to the BDI Process Flow screens to restart a failed BDI Flow. This action is not needed anymore. The failed BDI job is now restartable from the POM Batch Monitoring screen. POM identifies the failed subflows and only restarts them, thereby ensuring data integrity.
Change in Format of Notification Tab in Exported Spreadsheet
The format of the Notifications tab of the configuration spreadsheet exported on the Batch Administration screen has changed. Previously, notification types were each in their own row with email addresses being in a column and retention period in the next column. This is now reversed where notification types are in columns. By default, there is a row for ALL (schedules). Email addresses appear under each notification type for which an email notification is sent.
Also, by default, there is a row for the batch schedule being exported. This is because notifications are now configured at either the POM instance level (the ALL row) or the schedule level (the schedule row, for example: /MERCH).
In the above example, Callback failure notification emails are sent to Jane Doe for all batch schedules of the POM instance. Error notifications are sent to John Doe for only the Merch schedule.