1 Overview

Oracle Retail Brand Compliance Management Cloud Service 26.2.401.0 is a Critical Update.

Note:

For a description of recent enhancements for this application, see the previous Release Readiness Guide on Oracle Help Center.

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

There are no Database Upgrade Scripts included with this release.

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.

IDCS Changes

As part of the updates from release 20.0 onwards, there are a few changes into various records within the IDCS configuration. These changes should be considered in instances where you have adopted your own changes and configuration within IDCS.

Oracle Cloud Service Records

This section within IDCS is only accessible to Admin users of the IDCS tenancy. A new Cloud Service record is created for the release 20+ instance and is now named using the following naming structure:

  • STAGE: RGBU_BCCS_STG1_BC (from RGBU_BCCS_UAT_PROD_BC)
  • PROD: RGBU_BCCS_PRD1_BC (from RGBU_BCCS_PRD_PROD_BC)
  • DEV: RGBU_BCCS_DEV1_BC (from RGBU_BCCS_DEV_PROD_BC)

Where the OPAL Artwork is utilized, a new Cloud Service record is created for the release 20+ instance and is now using the following naming structure:

  • STAGE: RGBU_BCCS_STG1_ARTWORK (from RGBU_BCCS_UAT_PROD_ARTWORK)
  • PROD: RGBU_BCCS_PRD1_ARTWORK (from RGBU_BCCS_PRD_PROD_ARTWORK)

IDCS Group Records

These are created automatically by the Brand Compliance application and the naming of the groups is updated to be aligned with the Oracle Cloud Service record. Standard groups are created for . . . Artwork, . . . BC_User, . . . Reports_Admin, . . . Retailer, and . . . Supplier. For example, RGBU_BCCS_PRD1_BC_User is the new release 20+ group naming structure, RGBU_BCCS_PRD_PROD_BC_User being the previous naming structure.

Note:

When creating new groups within an IDCS tenant, avoid using the RGBU_BCCS_PRD1_ or RGBU_BCCS_STG1_ prefix for the name of groups. Any groups created with either prefix may have their users removed from the group as part of the hourly IDCS sync process.