1 Feature Summary
This chapter describes the feature enhancements in this release.
Noteworthy Enhancements
Note:
Oracle Retail has adopted a new numbering system to correlate the release numbers with Major Updates and the calendar for better clarity. The first two digits are the calendar year; the next digit is the Major release number; the third three digits reflect the calendar quarter and the month within that quarter; and the final digit represents the hot fix sequence.
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.
| Feature | Module Impacted | Scale | Delivered | Customer Action Required? |
|---|---|---|---|---|
|
All |
Small |
Enabled |
No |
|
|
All |
Small |
Enabled |
No |
Custom Job Types
For most retail applications such as Merchandising Foundation Cloud Services, batch schedules are based on Oracle pre-defined job types. These job types are associated with either the job’s shell script location or location of Rest APIs for running a job. In this release of POM, a user of certain retail applications such as Retail Data Store can define their own Custom Job Types. The user then associates a custom job type with access detail of the Rest APIs to start or restart or terminate a custom job. More information is provided in the Process Orchestration and Monitoring Implementation Guide.