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 Brand Compliance Management 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.

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

Resolved Issues

All

Small

Yes

No

Resolved Issues

This release includes resolutions to logged issues in various functional areas. For specific descriptions of the resolved issues, see Noteworthy Resolved Issues.

Post Release Tasks and 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.

Allergen Declaration Glossary

The fix for Commas in Allergen Declaration format (item 33012174, 33216825) may require a manual change to the Allergen Declarations glossary in the Products / Global Glossaries / Declaration part of Admin area.

Any Declarations that have a value of and as the End Separator (within the Format page) must be updated to insert a leading space, as a leading space will no longer be automatically inserted in the generated declaration. This must also be done for any language translations.

Permissions

For existing installations, the Creating new Activity Sub Status fix (item 31881501) requires a change to the Permissions spreadsheet in order to allow the Project Administrator to create new entries in the Activity Sub-Status glossary.

In the MyProject page, change the row with Authority Profile = Project Administrator and Data Record=ACTIVITY SUB STATUS to have an Access Level of C (instead of W):

Record (A) Authority Profile (B) Menu Option (C) Sub Menu Option (D) Action (E) Data Record (F) User Mode (L) Access Level (M)

MyProject

Project Administrator

      

ACTIVITY SUB STATUS

NORMAL

C

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.

System Text

The fix for the Specification Change History language translation (item 32211975) introduces two new entries to the Misc system text area: 

remove=Remove 
change=Change

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

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.

Enabling Artwork with SSO

Artwork is not a core Brand Compliance module, but a third-party add-on application. This process enables the integration with the third-party Artwork application, where it is used.

For existing installations that use the Artwork module, in order to configure single sign on (SSO) between Brand Compliance and the Artwork solution (using IDCS OR OCI IAM authentication), the following steps must be taken by the Customer or their Partner:

  1. Ensure the MYARTWORK external system has been created in Brand Compliance PROD and STAGE.

  2. Raise an SR service requesting for creation of the Artwork Application for PROD and STAGE. The call back URLs and IDCS OR OCI IAM URLs must be provided in the SR.

  3. Once created, you will be able to gather the Client ID and Client Secret from IDCS OR OCI IAM.

Refer to the Artwork chapter in the Oracle Retail Brand Compliance Management Cloud Service Administration Guide for the full process for enabling Artwork with SSO.