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 Supplier Evaluation 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.

Note:

Where new fields, User Interface (UI) changes, or glossary entries are introduced as part of a change, the portal owner may need to apply their own translations of the core system text.

Column Definitions

  • Feature: Provides a description of the feature being delivered.

  • Module Impacted: Identifies the module impacted 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.

Table 1-1 Noteworthy Enhancements

Feature Module Impacted Scale Delivered Customer Action Required?
Supplier and Site Address Validation

Supplier

Small

No

Yes
Project and Activity API Updates Process Medium

No

 Yes

Supplier and Site Address Validation

Currently there is no validation of Supplier and Site addresses and phone numbers, meaning that this information is often not completed. This enhancement allows validation to be applied when the supplier is confirming that their details are up to date, making the fields mandatory.

The validation is optionally applied by three new system parameters, providing control over which of the individual address and phone number fields are to be mandatory when the Confirm Details action is used on the Supplier or Site record.

By default, in a new portal and in an upgraded portal, the system parameters will not be set, meaning that the mandatory validation will not be applied. Clients can choose to set the parameters to enable the validation. See Post Release Tasks.

The new system parameters are:

  • The Supplier & Site Local Address Validation parameter allows selection of which of the Address fields mandatory validation is to be applied: Country, Address Line 1, Address Line 2, Address Line 3, Address Line 4, Post Code, GPS.
  • The Supplier & Site Business Language Address Validation parameter allows selection of which of the Business Language Address fields mandatory validation is to be applied: Country, Address Line 1, Address Line 2, Address Line 3, Address Line 4, Post Code.
  • The Supplier & Site Phone Mandatory parameter allows mandatory validation to be applied to the Phone fields.

If any of the selected fields fail the mandatory validation, the Confirm Details action will not take effect.

Project and Activity API Updates

The existing Project and Activity REST APIs are extended to allow for the update of Process (Project) and Activity records.

The following features are introduced:

  • Project API Project Update function

    An inbound PROJECT UPDATE endpoint to perform a PATCH update of Project/Process records. This allows for updates to individual attributes without having to submit the full record.

  • Activity API Activity Update function

    An inbound ACTIVITY UPDATE endpoint to perform a PATCH update of Activity records. This allows for updates to individual attributes without having to submit the full record.

    An inbound ACTIVITY STATUS UPDATE endpoint to update Activity status. The purpose of this endpoint is specifically to update the status, triggering any further updates to the associated Process or to other Activities within the Process.

  • Support for JSON format payload

    While the XML payload format continues to be available, support for the JSON payload format is added for the Project and Activity APIs.

Note:

The enhancement does not include the facility to create (POST) Project/Process or Activity records.

Typical usage would be for the following updates from external systems:

  • Process Schedule start or End Dates
  • Process attributes, including Custom Fields and Process Briefs
  • Activity Briefs
  • Activity Dates, including planned (scheduled) Start and End dates and Actual Start and End dates
  • Activity Status

Post Release Tasks & Impact on Existing Installation

The following post release tasks and impact on an existing installation must be taken into account as part of this release.

Database Update Scripts

The following feature includes a database upgrade script:

Site Workflow: Set to Awaiting Approval

Since this feature involves a modification to the allowable sequence and transition between statuses in the Site workflow, an update script will be applied to all Site records as part of the upgrade, to replace the existing workflow with the new modified workflow.

System Text

The Supplier and Site Address Validation feature includes new system text.

System text records are added automatically during the release process, however any translation overrides must be added manually, by the retailer administrator.

Post Release Configuration and Testing

The following feature has post release configuration and testing requirements.

Supplier and Site Address Validation

To enable the Supplier and Site Address Validation, set the following system parameters in the Registration page to apply the required mandatory validation:

  • Supplier and Site Local Address Validation - select which Address fields are to have mandatory validation applied: Country, Address Line 1, Address Line 2, Address Line 3, Address Line 4, Post Code, GPS.
  • Supplier and Site Business Language Address Validation - select which Business Language Address fields are to have mandatory validation applied: Country, Address Line 1, Address Line 2, Address Line 3, Address Line 4, Post Code.
  • Supplier and Site Phone Mandatory - set if mandatory validation of the Phone fields is required.

Since this enhancement involves a change to the Specification workflow, it is advised to include a business test of Specification progression through the workflow when upgrading to a release where this enhancement is included.

Enabling Identity Management Notifications

As an IDCS or OCI IAM Administrator, verify that Notifications are enabled in the corresponding Stage / Production tenant.

Enabling User Roles

If they do not already exist, configure the Power User, Account Administrator, Assistant Technologist, and Site Inspector user roles, and assign to the appropriate users.

The instructions for downloading and uploading the amended Permissions spreadsheet are as follows:

  1. Log in as an Oracle Authorized Administrator user and go to Company > Admin > Roles & Permissions.

  2. Open the Permissions page.

  3. Download the active spreadsheet by selecting the row with true in the Active Permissions column, click Download Selected, and save locally.

  4. Edit the downloaded spreadsheet, make the changes described above, then save the spreadsheet.

  5. Upload the edited spreadsheet by clicking Upload Permissions, select the spreadsheet, and click Ok.

  6. Apply the changes by selecting the uploaded spreadsheet row, click Process Selected, and then click Ok to confirm.