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.

Note:

An update to the generally-available documentation for this release is in progress.

Table 1-1 Noteworthy Enhancements

Feature	Module Impacted	Scale	Delivered	Customer Action Required?
JET UI List Views	All	Large	Yes	No
Delegate Functionality	Workspace	Small	Yes	Yes

JET UI List Views

The JET UI Workspace user experience is extended in this release to provide navigation across all functional list views – for all modules and sub modules excluding the administration list views in the Admin area.

The new Workspace list view designs already implemented for Announcements and Assignments are enhanced to include:

A set of system-delivered list views is provided for each option in the Tasks menu - the Company, Supplier, Product, Process, Library, and Reports modules. Each has a default view and may have alternative views.
The user may create and save their own personal views of custom columns and filter combinations.

A facility for migrating personal views from classic Brand Compliance is available.

The categorized list view pattern comprises a left-hand category pane (grouping by a key attribute), a central grid of rows and columns (representing the records and their attributes), with a toolbar containing the actions and searches, plus a set of filter tiles, and a slide-out data panel.
The hierarchical list view pattern has the same features as a categorized view, but in place of the category pane it has a hierarchical tree of nested entities. This is used for example for Library Documents, where the hierarchy is the document folders, and for Process Activities, where the hierarchy is the parent processes.
The list view grid’s toolbar standardizes the options for managing the view and actioning its contents:
- Actions menu - options for creating, updating, deleting records, applying workflow actions, and so on.
- Manage Columns - for adding, removing, and moving columns within the grid.
- Query by Example - for quick search filtering by column.
- Query Builder - for more complex searching, by the construction of query statements.
- Export options - for exporting the grid contents to an Excel, CSV, or XML data file.
- Sorting - the contents of the grid can be re-sequenced by any of its columns, by clicking the heading.

The set of filter tiles will apply predefined filters to the grid. The tile may contain a drill-down segment or a metric to indicate the number of related rows.
The data panel slides out to show additional information related to the selected row.

Until the JET UI forms are implemented, opening a record from the list view will present it in the classic Brand Compliance. The more complex actions and wizards will also launch the classic Brand Compliance form.

As part of the navigation changes, in order to better differentiate between the lists of retailer and supplier users, the option to view supplier users from the Supplier/Company menu is renamed from Users to Supplier Users.

Delegate Functionality

The existing Delegate facility in classic Brand Compliance, where a user can grant other users access to their list of tasks is implemented in the JET UI Workspace, providing the equivalent functionality for Assignments.

A user may allow other users to access their Assignments, to action them on their behalf, such as to cover a period of absence. Designating a Team Manager and Delegates in the User record grants those users the ability to view Assignments by switching the user in the Assignments Due pane, refreshing the lists of Assignments accordingly. The selected user's Assignments are shown until switching to another user (the current user’s name always appears at the top of the list), or the Workspace session is restarted.

This feature is only available to internal/retailer users. It is not available to external/supplier users.

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.

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.

System Text

The system text records for the Validation Override columns added to report queries (item 33551459) are as follows:

reportQueryColumn.ALLERGEN_OVERRIDE_COMMENTS=Validation Override Comments 
reportQueryColumn.ALLERGEN_OVERRIDE_REASON=Validation Override Reason
reportQueryColumn.ALLERGEN_OVERRIDE_APPROVAL_NAME=Validation Override Approval Name
reportQueryColumn.ALLERGEN_OVERRIDE_APPROVED=Validation Override Approved
reportQueryColumn.ALLERGEN_OVERRIDE_REQUEST_OVERRIDE=Validation Override Request Override
reportQueryColumn.VALIDATION_FAILURE_DESCRIPTION=Validation Override Reasons for Validation Failure

The system text record for the Process Status column added to the Process Activity list views (item 34975623) is as follows:

activityProjectStatus=Process Status

The Character Length Validation change (item 34828323) introduces a new error message:

maximumBytes=Value of {0} is too long, must be {1} bytes or less

The system text record for the new identity provider Synchronisation system parameter (item 34583511, 35223753, 35409416) is:

includeAllUsersInBcToIdcsSync=Include 'Login Disabled' Users in the Synchronisation

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

Custom Reports

For the Surveillance Testing Requirements reports change (item 33440787, 33769929), any existing custom reports that are based on the Surveillance As Sold and Surveillance As Consumed report queries may need to be amended to apply Surveillance Classification filters, if the report is to just include specific Physical, Microbiological, or Chemical classifications.

System Parameters

A new Include 'Login Disabled' Users in the Synchronisation system parameter is introduced to control the synchronization of User/External System accounts with the IDCS or OCI IAM identity management service (item 34583511, 35223753, 5409416). The default setting is to include all accounts in the synchronization, both active and disabled (the parameter is checked). This can be changed, as required by the system administrator.

Database Update Scripts

There are no Database Upgrade Scripts included within 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:

Log in as an Oracle Authorized Administrator user and go to Company > Admin > Roles & Permissions.
Open the Permissions page.
Download the active spreadsheet by selecting the row with true in the Active Permissions column, click Download Selected, and save locally.
Edit the downloaded spreadsheet, make the changes described above, then save the spreadsheet.
Upload the edited spreadsheet by clicking Upload Permissions, select the spreadsheet, and click Ok.
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:

Ensure the MYARTWORK external system has been created in Brand Compliance PROD and STAGE.
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.
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.