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?
JET UI Site Form <BETA> Supplier Medium No Enable JET UI forms.
Site Reference Attachment Linking Supplier Small Yes Update reference type glossary items if the attachment field is to be mandatory.

JET UI Site Form <BETA>

This release includes the Site form as part of the transition of forms to the new JET UI design. This is BETA release of the form and additional updates will be included within upcoming releases. Two notable areas that will be included later are Process Links and Linked Site sections.

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.

The Site Details page contains several tabs covering key information for the site.

The Main Details provides the sites main information, including contact details and technologist details.

Main Details screen

The Sourcing Details includes production details, billing details and grower details.

Sourcing Details screen

The References includes a table of references used by the site.

References screen

The Scores page contains the Score Details tab which the Evaluation Scores for the site and a summary of the records used to generate the scores.

Scores screen

The Contacts page provides a list view of contacts configured for the site.

Contacts Details screen

The Associated Records page provides a number of list view for associated record types through the available tabs.

Associated Records screen

Site Reference Attachment Linking

This is an enhancement to the Site References table on the Site form so that it is now possible to associate a row in the reference table with one or more attachments that have been saved against the Site record.

Where a row in the table needs to be evidenced by a certificate or other document, this will facilitate that.

Additionally, the Reference Type Glossary has been updated so that for each reference type it is now possible to configure whether the attachment is mandatory or not.

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.1.201.0 for additional post release tasks.

Database Update Scripts

There are no database update scripts included for this release.

System Text

The following features include new system text:

  • JET UI Site Form
  • Site Reference Attachment Linking

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:

  • Site Reference Attachment Linking
Site Reference Attachment Linking
  • If reference types are required to be mandatory, then set the new mandatory flag on each of the reference types where that is required.
  • Verify that the Site then validates the reference types appropriately when added against a Site record.
  • Reports

    The Site Reference query has been updated to include the “Linked Attachments” field to allow reporting on this new information.

  • Site Extract and RDS

    The RDS tables which include Site data have been updated to include the “Linked Attachments” field.

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.

  • Site REST API: The Site Reference Attachment Linking feature adds “Linked Attachments” from the Reference table.

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.