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.

  • 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?
Advanced Packaging Additional Information Validation	Product	Small	Yes	Optional glossary review
Current Specification List Views	Product	Small	Yes	No
Additional Updates to Site Form	Supplier	Medium	Yes	No
Global Network Bus (GNB) Conversion to JET UI	Global Network Bus	Small	Yes	No

Advanced Packaging Additional Information Validation

Advanced Packaging Additional Information questions can now be configured with separate validation requirements for Yes and No responses:

• Component Mandatory If Yes
• Component Mandatory If No

This provides greater flexibility and reduces unnecessary validation messages when Packaging Components are not applicable.

Existing glossary records are managed during the upgrade to preserve current behavior.

Current Specification List Views

Two additional Product Specification list views are now available: one for retailer users and one for supplier users.

These new views are designed to make it easier to locate and manage active specifications by excluding historical and draft records that are no longer part of day-to-day specification management activities. Excluded statuses are Draft, Superseded, De-listed, and Deleted.

The retailer view is based on the existing Specifications by Technologist list view. The supplier view is based on the existing Specifications by Site list view.

Note:

This enhancement applies to environments that have the JET UI enabled.

Additional Updates to Site Form

As part of the ongoing transition to the JET UI framework, additional changes for the JET UI site form are included in this release. The additional updates include Linked Sites and Process Links.

With JET UI enabled, the new JET UI Site form can be enabled with the JET UI Forms Enabled system parameter; or individual users can enable the forms using the new Preview JET UI Forms setting in their User Preferences

Note:

This enhancement applies to environments that have the JET UI enabled.

Global Network Bus (GNB) Conversion to JET UI

The Global Network Bus user interface has been updated so it will provide a more consistent look and feel across Oracle Retail applications. The update improves usability and accessibility while preserving existing functionality. No changes are required to current business processes.

Note:

This enhancement applies to environments that have the JET UI enabled.

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.

Note:

See the Noteworthy Resolved Issues document for 26.2.301.0 for additional post release tasks.

Database Update Scripts

An upgrade data script will automatically update existing Additional Information Question glossary records to reflect existing behavior.

Permissions

There are no new permissions in this release.

System Text

The following features include new system text:

• Advanced Packaging Additional Information Validation
• Current Specification List Views
• Additional Updates to Site Form

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 features have post release configuration and testing requirements:

• Advanced Packaging Additional Information Validation
• Current Specification List Views
• Additional Updates to Site Form

Advanced Packaging Additional Information Validation

• Configuration

  Review and update Additional Packaging Information Question glossary records to take advantage of the new validation options.

• Testing Guidance

  Review existing Additional Packaging Information Question glossary records to ensure current behavior is preserved as follows:

  • If the Component Mandatory checkbox was not previously checked, then neither of the new checkboxes will be checked.
  • If the Component Mandatory checkbox was previously checked, then both of the new checkboxes will be checked.

  Verify that validation behaves as expected for Yes and No responses.

• RDS

  The RDS tables have been updated to include the new validation settings from the Additional Information Question glossary.

Current Specification List Views

• Configuration

  No configuration is required. The new list views are automatically available following upgrade.

• Testing Guidance

  Customer release acceptance testing should include the Specification list views and verify that active specifications are displayed as expected and that historical and draft records are excluded.

Additional Updates to Site Form

• Configuration

  No configuration is required. The updates to the form are automatically available following upgrade.

• Testing Guidance

  Customer release acceptance testing should include a general review of the Site form and its key features to ensure creating and editing functionality behaves as expected.

Application Program Interfaces (APIs)

The following API is affected by this release. Consider if changes need to be made to any external systems that call the API.

• Specification REST API: When updating an existing specification through the API, section change logs are preserved and cannot be removed or altered by the update payload. New changes are appended, ensuring historical section changes remain intact.

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.

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.

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.