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. There fore, the potential impact to users is minimal.

  • Larger: 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?
Additional Fields in Embedded Views	Supplier	Small	Yes	No
Additional OLC BI Publisher Reports	Reports	Small	No Reports need to be scheduled	Yes
Audit Email Notifications	Supplier	Small	No System parameters need to be updated	Yes
Confirm Supplier and/or Site Email Notifications	Supplier	Small	Yes	No
Country of Origin Selectors	Product	Larger	No	Yes
Delisting Sites	Supplier	Small	Yes	No
Design Agency Language Preferences	Product	Small	No	Yes
Project Spreadsheet Import and Download	Project	Small	No	Yes
Scorecard Email Notifications	Supplier	Small	Yes	No
Spec Archiving Batch Jobs	Product	Small	Yes	No
Supplier and Site GLN	Supplier	Small	Yes	No
Time Zone Parameter	Supplier	Small	No Parameter needs to be set	Yes

Additional Fields in Embedded Views

Additional columns are added to the following embedded list views:

• Site Status in the Sites page of the Supplier record.

• Product Status in the Product Records page of the Supplier and Site records.

Additional OLC BI Publisher Reports

To supplement the existing Claims & Statements reports, the following additional reports will be available:

Report	Description
CR87 Food Other Labelling Copy	The report is based on the OLC section of the Food Specification. It contains any specifications which meet the filter criteria entered by the user. Filters may be based on any fields available in the Other Labelling Copy data source query. Tabular data will not be included, other than for the Shipping Case Codes, EAN/Barcodes, and Catch Weight Increments fields. Two alternative versions of the query/data source are provided, which output separate rows for the contents of the EAN/Barcode and Shipping Case Code tables, for the creation of custom variants of the report. OLC EAN Barcodes: A row per entry in the EAN/Barcodes table, with any Shipping Case Code values concatenated together and repeated for each row. OLC Shipping Case Codes: A row per entry in the Shipping Case Codes table, with any EAN/Barcodes values concatenated together and repeated for each row.
CR88 BWS Other Labelling Copy	The report is based on the OLC section of the BWS Specification. It contains any specifications which meet the filter criteria entered by the user. Filters may be based on any fields available in the Other Labelling Copy data source query. Tabular data will not be included, other than for the Shipping Case Codes, EAN/Barcodes, and Catch Weight Increments fields. Two alternative versions of the query/data source are provided, which output separate rows for the contents of the EAN/Barcode and Shipping Case Code tables, for the creation of custom variants of the report. OLC EAN Barcodes: A row per entry in the EAN/Barcodes table, with any Shipping Case Code values concatenated together and repeated for each row. OLC Shipping Case Codes: A row per entry in the Shipping Case Codes table, with any EAN/Barcodes values concatenated together and repeated for each row.
CR89 FNF Other Labelling Copy	The report is based on the OLC section of the FNF Specification. It contains any specifications which meet the filter criteria entered by the user. Filters may be based on any fields available in the Other Labelling Copy data source query. Tabular data will not be included, other than for the Shipping Case Codes and EAN/Barcodes fields. Two alternative versions of the query/data source are provided, which output separate rows for the contents of the EAN/Barcode and Shipping Case Code tables, for the creation of custom variants of the report. OLC EAN Barcodes: A row per entry in the EAN/Barcodes table, with any Shipping Case Code values concatenated together and repeated for each row. OLC Shipping Case Codes: A row per entry in the Shipping Case Codes table, with any EAN/Barcodes values concatenated together and repeated for each row.
CR90 CNF Other Labelling Copy	The report is based on the OLC section of the CNF Specification. It contains any specifications which meet the filter criteria entered by the user. Filters may be based on any fields available in the Other Labelling Copy data source query. Tabular data will not be included, other than for the Shipping Case Codes and EAN/Barcodes fields. Two alternative versions of the query/data source are provided, which output separate rows for the contents of the EAN/Barcode and Shipping Case Code tables, for the creation of custom variants of the report. OLC EAN Barcodes: A row per entry in the EAN/Barcodes table, with any Shipping Case Code values concatenated together and repeated for each row. OLC Shipping Case Codes: A row per entry in the Shipping Case Codes table, with any EAN/Barcodes values concatenated together and repeated for each row.
CR91 Produce Other Labelling Copy	The report is based on the OLC section of the Produce Specification. It contains any specifications which meet the filter criteria entered by the user. Filters may be based on any fields available in the Other Labelling Copy data source query. Tabular data will not be included, other than for the EAN/Barcodes and Catch Weight Increments fields. An alternative OLC EAN Barcodes version of the query/data source is provided, which outputs separate rows for the contents of the EAN/Barcode table, for the creation of custom variants of the report.
CR92 OLC Printer Details	The report is based on the OLC section of any specification type. It contains any specifications which meet the filter criteria entered by the user. Filters may be based on any fields available in the OLC Printer Details data source query. Blank rows in the Printers table (those where the Printer Name mandatory field is missing) are omitted from the report.

A single Other Labelling Copy data source query will provide all the required fields that can be utilized to create a report from more than one specification type if required.

In addition, an OLC Printers Report will also be available which reports on the Printers table in the OLC sections.

Audit Email Notifications

Due and overdue audit notifications appear in the Task App and UIM but are often missed if users do not regularly log in to the system. Now due and overdue audit email notifications will also be generated on a daily basis dependent upon new system parameters.

The email notification recipients are the Person Responsible named in the Audit/Visit and the Supplier and Site’s Audit and Visit Contact.

New system parameters will provide a mechanism to determine if retailer and /or supplier users will receive the audit email notifications.

Supplier users will not receive these notifications for any audit/visit that is set to unannounced.

Email Templates

Two new email templates, AUDITVISITDUE and AUDITVISTOVERDUE, will be used to provide details of an audit/visit due or overdue. These templates will be available in the Admin area with the existing templates.

Confirm Supplier and/or Site Email Notifications

Supplier users get Urgent Item notifications to Confirm Supplier Details and Confirm Site Details, but these are often missed if users do not regularly log in to the system. Now users will receive email notifications to confirm Supplier and/or Site details.

The email notification recipients will be the Supplier Administrator and/or Site Administrator based on the supplier/site. The batch job to generate the email notifications will utilize the time zone parameter if set.

Email Templates

The new email template, CONFIRMDETAILSREMINDER, will be used to provide details of the relevant Supplier and Sites needing confirmation. The templates will be available in the Admin area with the existing templates.

This feature is enabled by default so emails will start to be sent once the application has been updated. If the emails are not required, the template can be disabled. See Post Release Tasks for details.

Country of Origin Selectors

Enhancements to increase the amount of detail captured in a Product Specification regarding the product's country of origin:

• The current Country of Origin selector in the Other Labelling Copy (OLC) section allows multiple countries to be selected.

• A new field in the Food and Produce specifications for specifying the country of origin of the product’s primary ingredients.

All Country of Origin data will be available for inclusion in reports that use the Products Country of Origin and Label Claims Statements data sources (BI Publisher only). Pack Copy files in preview or when generated will also include the new Country of Origin data from the OLC section.

The new field will be available in the Specification Extract for the different specification types. The Specifications API will also be extended, to include the Country of Origins fields but will continue to hold the existing single value Country of Origin field for backward compatibility.

Delisting Sites

An enhancement to help improve the process of delisting Sites by notifying the user if the site being delisted has active Products or Specifications associated to it. This is to encourage the user to archive or deactivate the associated records before delisting the site.

Design Agency Language Preferences

The Design Agency and Counter Ticket Producer configuration records are used to send the Design Agency/Counter Ticket Producer contact an email containing the product specification Pack Copy/Counter Ticket files. A language preference will be available to add to the Design Agency and Counter Ticket Producer glossary records, to set the language of the Pack Copy File notification email. If no preference is set, the default base language will be used.

Project Spreadsheet Import and Download

The addition of a facility for importing Projects from a spreadsheet. The import allows for the creation of Projects only; it cannot be used to update existing Projects.

Scorecard Email Notifications

Currently, there is just one email associated with Scorecards, which is sent to users when the Scorecard is overdue, but there is no email when the Scorecard changes status, requiring action. A new email notification will now be sent when the Scorecard changes status to Awaiting Amendment. The email notification will be sent to Supplier or Site users with the Contact Roles set against the associated Scorecard Template.

Email Templates

The new email template SCORECARD_STATUS_CHANGE will be used for sending email notifications of a Scorecard status change to Awaiting Amendment. The templates will be available in the Admin area with the existing templates for new installations but will need adding for existing.

Spec Archiving Batch Jobs

The timing of the batch jobs and the time zone of client systems means that there may have been a delay with archiving some specifications. Now the specification archiving batch jobs will run hourly and the trigger criteria will also utilize the System Time Zone parameter if set. This impacts the produce specifications and temporary specifications.

Supplier and Site GLN

New fields on the Supplier and Site records for the capture of GLN (Global Location Number) identity codes have been added.

System parameters are available, to allow configuration rules for validating the fields to be implemented and whether the fields are mandatory. The standard GS1 GLN mechanism is 13 digits, including the check digit. The check digit calculation is the same as the existing barcode and shipping case check digit calculation.

Time Zone Parameter

To enable batch jobs to be run on client systems at expected times, a new Global system parameter will allow the client system to be associated with a time zone. The parameter is optional and will only be utilized if set. This parameter will initially be used to offset certain new batch jobs. All other existing batch jobs will remain based on UTC as they currently are.

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.

Additional OLC BI Publisher Reports

For new reports to run, they need to be scheduled as required.

Audits & Visits Emails

Audit & Visit due and overdue email notifications are generated by a scheduled job based on the existing Task App Audit/Visit due notifications criteria and the Urgent Items Manager Audit/Visit overdue notification criteria. The process will utilize the System Time Zone parameter if set.

Due notifications (Task App and email) utilize the existing Days to show Schedule in Task App system parameter. If not set, a default value of 28 days is assumed for due notifications.

Overdue notifications (UIM and email) utilize the existing No Days before Audits and Visits are Overdue system parameter. If this is set to blank, no overdue notifications are sent.

For upgrades and new installations, the initial default setting of the system parameters which control who receives notifications will be unchecked (No) so that no email notifications are sent. These system parameters should be updated as appropriate if the email notifications to active users are required:

• Send Audit/Visit Due Notifications to Supplier*

• Send Audit/Visit Due Notifications to Retailer

• Send Audit/Visit Overdue Notifications to Supplier*

• Send Audit/Visit Overdue Notifications to Retailer

* Any Audit/Visit that has Announced set to No, the Supplier recipients will not receive due or overdue notifications for the given audit/visit.

The new Audit/Visit email templates (AUDITVISITDUE, AUDITVISITOVERDUE) can be customized by the administrator, if required.

Confirm Supplier/Site Emails

For upgrades and new installations, the scheduled job associated with sending of the new email notifications for confirming supplier/site details will run automatically without user intervention. This means they will be sent once the system is installed /upgraded based on existing notifications to confirm supplier/site details in the UIM. If this is not required, the email template can be disabled, by a System Administrator setting the CONFIRMDETAILREMINDER email template to disabled, in the Admin-Notifications area.

This functionality utilizes the System Time Zone parameter if set.

The new Supplier/Site email template (CONFIRMDETAILSREMINDER) can be customized by the administrator, if required.

Country of Origin Selectors

For existing installations, the Country of Origin fields in the Product Specification are automatically converted to multi-value fields as part of the upgrade. The existing single-value fields are retained, for continued use in Jasper reports and the Specifications API. If multiple selections have been made, the single-value field holds the first in the list. The single-value fields will be removed in the future.

The new Primary Ingredients Country of Origin must be set up by the administrator if it is to be used. The field will appear in the Food and Produce specifications that were created prior to the upgrade, but no value will be present until the specification is subsequently edited, and a selection made.

The new fields are included in the following:

• Specifications API

  The existing Country of Origin field becomes a multi-value field. The single-value field will remain in the XML payload for backward compatibility. If multiple countries have been selected in the specification, the single-value field will just contain the first in the list. When creating or updating a specification using the REST API, if the XML only has the single-value field populated, that value will be automatically written to the multi-value field. The single-value field will eventually be removed.

  The API includes additional nodes but remains backwards compatible with the previous version. However, consider whether any changes are necessary to the existing usage of the API, to handle the additional data that is now available.

• Specifications API Reports Data Source

  The new Country of Origin data is available for inclusion in reports (and Pack Copy files). Create new report designs and schedules for any reporting requirements.

  For existing reports that have filters based on the Country of Origin fields, where the filters currently use the EQUALS operator, this will continue to work following conversion from a single to multi-value field. However, once the field is populated with more than one country, the filter will no longer match, so it will be necessary to change the operator from EQUALS to CONTAINS.

  Note: The new Primary Ingredients Country of Origin field and multi-value Country of Origin fields are only available to BI Publisher reports; they are not available to legacy Jasper reports.

• Specifications Data Extract

  The existing single-value Country of Origin columns in the extract CSV files has multiple values concatenated in comma-separated list. Note that columns GC onwards are advanced in the Produce Extract file to accommodate the new field in column GC.

Design Agency Language Preference

For existing systems, if the alternative language options are required, the Design Agency/Counter Ticket Producer glossary records must be updated to assign the appropriate language.

Project Spreadsheet Import

For existing installations, the following change must be made to the Permissions spreadsheet to provide the Project Administrator and Project Manager with the ability to access the batch jobs, to view the progress of Project Import jobs.

Add the following rows to the Admin page:

Record	Authority Profile	Menu Option	Sub Menu Option	Action	Data Record						User Mode	Access Level
Admin	Project Administrator				BATCH JOB						NORMAL	R
Admin	Project Manager				BATCH JOB						NORMAL	R
Admin	Project Administrator	Admin	BATCH JOB								NORMAL	Y
Admin	Project Manager	Admin	BATCH JOB								NORMAL	Y

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 and click Process Selected, then Ok to confirm.

Scorecard Email Notifications

The new Scorecard email template (SCORE3) can be customized by the administrator, if required.

Spec Archiving Batch Jobs

The Spec Archiving Batch Jobs is an existing process that ran daily but which will now run hourly. No user intervention for either a new install or upgrade is required. The process will utilize the System Time Zone parameter if set.

Supplier and Site GLN

The default settings of the new GLN Codes system parameters do not apply validation, in order to match the behavior in existing systems. Change the default settings, if required.

Time Zone Parameter

For new installations and upgrades, there will be no initial value set against the System Time Zone parameter, which means the system will continue to use the UTC time zone. The parameter should be updated to reflect the client system time zone if required.

Order of Columns in Nutrition Declaration Panel

For this fix (items 32046778, 32062296), any specifications that have been re-versioned or copied should be verified to ensure that the Nutrition columns are in the correct order as defined by the Nutrition Panel. Any that are found to be different will need to be regenerated on the Nutrition section. This could involve changing a specification status back to a status where this can be edited, or a new version of a specification created if already at active status.

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 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 URLs must be provided in the SR.

3. Once created, you will be able to gather the Client ID and Client Secret from IDCS.

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.