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?
Identity Provider Update

General

Small

Yes

Yes

Identity Provider Update

Identity Provider Update is the relocation of the existing IDCS admin console User Interface to the OCI Console. Although the changes in functionality for Brand Compliance are behind the scenes, there is a requirement to update all references to IDCS within the application and the documentation to provide correct and consistent references.

Changes have been made so the text Identity Provider is displayed where previously it was IDCS, Identity Cloud Service, or Identity Management.

These text changes are visible in the following areas where the text is used:

  • Landing Page

  • Home Page

  • System Parameters

  • User Record

  • Email Template - Body field

  • Batch Job - Job Type, Description, and Message fields

Some of the changes required System Text updates, to manage the text displayed in the application. See Post Release Tasks for further details.

Note: The User Interface for the Identity Management solution changes when upgraded from IDCS to that within the OCI Console. This upgrade is handled outside of Brand Compliance; contact your CSM contact for more information as to when the IDCS console will be switched over to the OCI Console.

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.

Identity Provider Update

System Text records using the following text, in the Description field, have been replaced with Identity Provider:

  • IDCS

  • Identity Cloud Service

  • Open Identity Management

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

Email Templates IDCS1 and IDCS2 records require manual updates to replace text Identity Management with Identity Provider in the Body field. In addition, any language translations required will also require a manual update.

System Text

The fix to include the Period field in the Pack Coding query (33503861) introduces a new System Text record:

reportQueryColumn.PACK_CODE_PERIOD=Period

The fix to include the Spec Type field in the Product query (33378451) introduces a new System Text record:

reportQueryColumn.PRODUCT_RECORD_SPECIFICATION_TYPE=Product Record - Spec Type

The fix to include the Tamper Evident field in the Advanced Packaging Component query (33246837) introduces a new System Text record: 

reportQueryColumn.ADV_PACKAGING_COMPONENT_TAMPER_EVIDENT=Packaging Component Tamper Evident

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.