| Oracle® Retail Brand Compliance Management Cloud Service Release Notes Release 18.3 F26784-03 |
|
 Previous |
| Oracle® Retail Brand Compliance Management Cloud Service Release Notes Release 18.3 F26784-03 |
|
Previous |
Release Notes
Release 18.3
F26784-03
September 2020
This document highlights the major changes for Release 18.3 of Oracle Retail Brand Compliance Management Cloud Service.
Oracle Retail Brand Compliance Management Cloud Service is an application designed to meet all aspects of sourcing, developing, and protecting retailer brands. The application provides solutions for product development, compliance, quality, and traceability. It is designed specifically for retail, food service, and manufacturing businesses to develop and protect their brands, manage their suppliers, and ensure full end-to-end product lifecycle management.
Oracle Retail Brand Compliance Management Cloud Service is composed of the following modules:
Library enables the issue, receipt, and acceptance of policies, guidelines, and key working documents.
Product supports the development of products and production specifications.
Project supports the development of project briefs, plans, and workflow management.
Supplier enables the identification, selection, and approval of suppliers.
Reports - reporting tool for reporting across the system, using standard templates and custom reports.
Oracle Retail Brand Compliance Management Cloud Service is hosted in the Oracle Retail Cloud with the security features inherent to Oracle technology and a robust data center classification, providing significant uptime. The Oracle Cloud team is responsible for installing, monitoring, patching, and upgrading retail software.
Included in the service is continuous technical support, access to software feature enhancements, hardware upgrades, and disaster recovery. The Cloud Service model helps to free customer IT resources from the need to perform these tasks, giving retailers greater business agility to respond to changing technologies and to perform more value-added tasks focused on business processes and innovation.
Oracle Retail Software Cloud Service is acquired exclusively through a subscription service (SaaS) model. This shifts funding from a capital investment in software to an operational expense. Subscription-based pricing for retail applications offers flexibility and cost effectiveness.
The following technology is supported:
The following web browsers are supported:
|
Note: Oracle Retail assumes that the retailer has ensured its Operating System has been patched with all applicable Windows updates. |
Microsoft Internet Explorer 11
Mozilla Firefox ESR 68+
Google Chrome (Desktop) 79+
Edge 44+
|
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. |
The following functional enhancements are included in this release:
Various legislations utilize an overall Nutrition score, which is a single calculated score based on points awarded for the quantity of each specified nutrient. Examples are the Health Star ratings in Australia and the OFCOM nutritional scoring guidelines in the UK.
In some cases, the final score is used on the label, in others it is used to inform other retailer requirements, such as the ability to advertise the product or make other health claims, but the underlying principles are similar.
The facility is introduced to calculate nutrition scoring data within the product specification's Nutrition section, based on a set of configurable scoring rules per type of product.
The key features are as follows:
New system parameters enable the feature, in Food and/or Produce specification types, and set the default rules for whether the scores are to appear on pack.
A new Nutri-Score Categories glossary is introduced for the configuration of the different categories of product, for which scores are to be calculated. A list of nutrients has points assigned to ranges of Per 100g nutrition values. These rules can also be extended to modify the assigned number of points, based on the value of a related nutrient.
An associated Nutri-Score Scores glossary is used to convert the points total to an overall score value.
If the feature is enabled for a Food or Produce specification, the Nutrition section includes the ability to assign a Nutri-Score category, which results in the total number of points being automatically calculated and converted to the corresponding score value. The calculations use the rounded Per 100g nutrition values.
The user can choose whether the calculated score is to be included in the specification's Pack Copy file. The option is defaulted according to the setting of the system parameter.
The specification's Nutri-Score data is also included in the data formats used by the Specifications API (including the Global Network Bus synchronization), the Specifications Extract, and the Specifications Nutrition reporting data source.
The existing functionality available in the US legislation for declaring dual format As Sold and As Prepared nutrition values is made available to the following legislations:
Argentina
Brazil
Chile
EU (Europe)
India
Japan
Mexico
South Africa
Historically, for these legislations, either As Sold or As Prepared format has been declared, but there is a growing demand to declare both formats.
Currently, the Calculate Amounts option can be unchecked in the specification, which stops the system automatically calculating the Per Serving information from the Per 100g values, allowing the user to manually enter Per Serving As Prepared information, but this does not enable both formats to be used.
The Nutrition Panel configuration already has an As Prepared Values parameter, which extends the Nutrition table in the specification, to include Per 100g and Per Serving As Prepared columns for all legislations. However, for declaration purposes, these have only been used for US dual nutrition panels, which show both As Sold and As Prepared columns.
Therefore, the dual panel format declarations are being made to the above legislations, as follows:
For dual format panels, when the As Prepared Values option is in selected, it is possible to select the following columns to appear in the generated nutrition declaration:
Per 100 g/ml
Per Serving
% Reference Intake per 100 g/ml
% Reference Intake per Serving
Per 100g/ml As Prepared
Per Serving As Prepared
% Reference Intake per 100g/ml As Prepared
% Reference Intake per Serving As Prepared
Reference Intake
Score
The ordering of the columns in the Panel glossary determines the order the columns are to appear in the Declaration panel when it is generated in the Product Specification. See Post Release Tasks for further details.
All rounding rules for the declared As Prepared values are the same as for the corresponding As Sold declaration values.
When a dual format panel is used, the Front of Pack nutrition declaration is based on either the As Sold or As Prepared values.
The Which Data to be Used field allows As Prepared to be selected (the options are Per 100 Packaged, Per Serving Packaged, Per 100 Prepared, Per Serving Prepared). It controls which data is used in the Front of Pack declaration.
The following fields are used to determine which %RI values are displayed, and which values are used for the color coding calculations (the score):
% Reference Intake data to use - which RI values are displayed in the Front of Pack panel (options are % RI Per 100 Packaged, % RI Per Serving Packaged, % RI Per 100 As Prepared, and % RI Per Serving As Prepared).
Data to use for Score calculation, whether As Sold or As Prepared values are used to calculate the score (options are As Sold and As Prepared).
The score calculation uses both Per 100 and Per Serving values (according to the Serving Criteria Threshold set in the Scoring Rule configuration), so this field only controls whether the values used should be taken from the As Sold or As Prepared data.
The As Prepared/Served Text field provides the heading for the Per Serving As Prepared column in a dual format panel.
The As Prepared Per 100g Text field appears when the selected panel format has the As Prepared Values option checked. It provides the heading for the Per 100g As Prepared column (if the column is selected to be declared). A corresponding field in the panel's Defaults page enables default text to be set.
The Per 100g Text field provides the heading for the Per Serving As Sold column.
The Serving Quantity As Prepared value is used for calculating the As Prepared Per 100g/Per Serving values.
The Nutrition data entry table extends to include the As Prepared columns when the As Prepared Values option is set for the panel.
|
Note: As part of the enhancement, the Nutrition panel outputs for all legislations become a simple table, with all graphical formatting removed.The indenting of constituent nutrients is retained, with the first constituent preceded with of which. Also, the order of the columns in the Nutrition panel outputs for all legislations becomes controlled by the order set in the Available Columns table of the Nutrition Panel glossary record. See Post Release Tasks for further details. |
A fourth phase of standard BI Publisher report templates is made available within the Reports module. The new reports are available for scheduling, and may be copied and adapted to form custom variants.
The following standard reports are made available:
| Report | Description |
|---|---|
| CR17 Surveillance Testing Requirements - Product Attributes (As Sold) | Two versions: a) Surveillance Testing Requirements - Product Attributes (As Sold) for non-Produce specifications; b) Surveillance Testing Requirements - Product Attributes (As Sold - Produce) for Produce.
Based on the Finished Product Standards section, the report searches Product Specifications (all types) for those containing any Product Surveillance Classifications that match the specified value. The report lists details from the FPS Attributes tables. The report is from the perspective of the Specification, but pulls Surveillance Classifications from the Product record (except for Produce, which holds the surveillance classifications in the specification's Main Details section). |
| CR18 Surveillance Testing Requirements - Product Attributes (As Consumed) | Based on the Finished Product Standards section, the report searches Product Specifications (Food types) for those containing any Product Surveillance Classifications that match the specified filter values. The report lists details from the FPS Attributes tables. The report only includes products that have surveillance classifications present.
The report is from the perspective of the Specification, but pulls Surveillance Classifications from the Product record. |
| CR22 Surveillance Classifications | Two versions: a) Surveillance Classifications for non-Produce specifications; b) Surveillance Classifications (Produce).
The report searches Product Records (all types) for those containing any Product Surveillance Classifications that match the specified value. The report is from the perspective of the Product Record (except for Produce, which holds the surveillance classifications in the specification's Main Details section). |
| CR23 Surveillance Test Report Summary | Four versions: a) Surveillance Test Report Summary and b) Surveillance Test Report (per Supplier) for non-Produce specifications; c) Surveillance Test Report Summary (Produce) and d) Surveillance Test Report (per Supplier - Produce) for Produce.
The report searches Surveillance Test Reports based on the selected filters. Filter the date of sampling on either a date range or a relative date. Option is available to group the output by Supplier. |
| CR24 Surveillance Results by Date Range | The report provides a KPI trend analysis of completed surveillance reports, by supplier.
A monthly analysis of the number of completed Test Reports, within a date range is presented as table of the count of those with a completion date, sorted by test discipline, grouped by month of completion. Option is available to show the results by Test Score. |
| CR25 Surveillance Billing Report | Eight versions: a) Surveillance Billing Report, b) Surveillance Billing Report (per Supplier), c) Surveillance Billing Report (per Test Discipline), and d) Surveillance Billing Report (per Supplier and Test Discipline) for non-Produce specifications; e) Surveillance Billing Report (Produce), f) Surveillance Billing Report (per Supplier - Produce), g) Surveillance Billing Report (per Test Discipline - Produce), and h) Surveillance Billing Report (per Supplier and Test Discipline - Produce) for Produce.
The report searches Product Records (or the Product Specification Main Details section for Produce) by date range and supplier, showing test results and costs/billing details. Total cost is calculated by date range. Option is available to group the output by Supplier and/or Test Discipline. |
This section highlights specific key fixes that are included in this release. In some cases, only a percentage of the overall fixed defects are listed.
| Affected Component | Defect Number | Description |
|---|---|---|
| General: Users | 27375475 | Authority Profile selector visible to Supplier user
A fix has been made to rectify an issue with the Authority Profile selector becoming visible to Supplier and Site users. The selection of individual authority profiles is only applicable for Retailer users, so it is now hidden in the User record for Supplier and Site users. |
| General: Users | 29997359, 29997401 | Inconsistent Language and Time Zone defaults
A fix has been made to rectify an issue with the creation of new User accounts, where the setting of the user's language and time zone varied between taking the system default and that of the current user. The fix ensures consistency between the creation of Retailer and Supplier users, when setting the default language and time zone. For all types of users, the Language and Time Zone fields are now defaulted to the Language and Time Zone of the current user (that is, the user who is creating the new user account). |
| Global Network Bus: Contacts | 30567745 | Supplier Contact not found when synchronizing Product Specifications
A fix has been made to rectify an issue with supplier contacts not being included when synchronizing Product Specification data within the Global Network Bus. The issue resulted in soft deleted contacts not being found during lookup using the global id, because soft deleted rows were excluded from the query. |
| Global Network Bus: Specifications | 30556947 | Error when synchronizing Product Specification data
A fix has been made to rectify an error that occurred when synchronizing Product Specifications. The exception was related to the Find by spec number and version method. |
| Library: Readership Log | 30399028 | Error when downloading Readership Log
A fix has been made to rectify an error when downloading a Library document's readership log. The issue occurred when the log contained in excess of 2000 entries. The limit of 2000 entries is a fixed limit; instead of erroring, a message is now presented if the selected number of entries to download exceeds the limit. |
| Product: Product Records | 30963899, 30963964 | Error when adding variants to a Product Record
A fix has been made to rectify an error when a Supplier user added a product variant to an active Product Record. |
| Product: Specifications | 26647389 | Error when changing a Specification's Nutrition Panel type
A fix has been made to rectify an error when changing a specification's Nutrition Panel type. The error occurred where a lite panel type was changed to a different lite panel type. |
| Product: Specifications | 28431031, 29277513 | Unable to delist an active Product Specification
A fix has been made to rectify an issue with the delisting of active specifications. The issue occurred because of a terminal error being issued when attempting to delist a multi-pack specification with more than one product variant. The validation has been changed to issue a warning rather than a terminal error. |
| Product: Specifications | 29025303, 29488018 | Error when copying Supplier data within the CNF Components section
A fix has been made to rectify an error when copying a row with the Supplier details column populated within the Components section of the Constructed Non Food specification. |
| Product: Specifications | 29036495 | Columns to be Declared overwritten
A fix has been made to rectify an issue with the Columns to be Declared field in the header of the Nutrition section being reset to default values when creating a new version of the specification. |
| Product: Specifications | 29283523, 30655128 | Inactive entries appear in the Countries selector
A fix has been made to rectify an issue with inactive entries in the Countries glossary appearing in the picklist for selection within product specifications. The issue occurred in the Raw Materials table and dialog box in Food and Formulated Non Food specifications, and in the Component section of the Constructed Non Food specification. |
| Product: Specifications | 29396527, 29593864 | Error when progressing Specification to Pack Copy Sent status
A fix has been made to rectify an error when progressing a product specification to Pack Copy Sent status. The error occurred because the temporary folder used by the pack copy generation process had been deleted. |
| Product: Specifications | 29582930 | Custom fields not available for selection in list views
A fix has been made to rectify an issue where certain Custom fields were not available to add as columns in list views. The issue relates to the Rich Text Field 4 and Rich Text Field 5 user-defined fields. Note that where used, the default names of these fields may have been overridden to custom names. |
| Product: Specifications | 29865671, 29968486, 30009680, 30036389, 30055894 | Error when opening Chemical Standards in FPS section
A fix has been made to rectify an error when opening the Chemical Standards page in the Finished Product Standards specification section. The issue was caused by an inconsistent sequencing of the Chemical Standards table rows. |
| Product: Specifications | 29875591, 30085526, 30519764, 30633216 | Issues with Front of Pack Nutrition Scoring
A fix has been made to rectify an issue in the Front of Pack Nutrition Scoring Rules glossary, which is located in the Product Global Glossaries admin area. The issue resulted in rows of the Score Bandings table being hidden. The fix addresses a related issue where the front of pack nutrition score color coding was not present in the product specification's Nutrition section. |
| Product: Specifications | 29958804 | Issue with selection of Standards in FPS section
A fix has been made to rectify an issue with the description of selections from the Microbiological, Chemical and Physical standards in the Finished Product Standards specification section. The issue resulted in the description and code both showing as the description, and also affected the sequencing of the selections. |
| Product: Specifications | 30188601, 30326783 | Reason for Validation Overrides not retained in new version of Specification
A fix has been made to rectify an issue with the reason for a Validation Override not being retained in the Allergy & Dietary Advice section when creating a new version of a specification. The issue occurred when creating a new version of a specification that was at the Not Progressed status. The Validation Override details are now carried across to the new version of a specification; they are not carried across when a specification is copied to create a new specification. |
| Product: Specifications | 30326977 | Forced Addition missing from Recipe/Formulation Export file
A fix has been made to rectify an issue with the Forced Addition column in the Recipe table not appearing in the file generated by the Food specification's Recipe Export facility. The issue also occurred in the Formulated Non Food specification's Formulation Export facility. The recipe and formulation export/import file now contains the Forced Addition values regardless of whether they were entered as a free text field or as a glossary selection. Previously, the value was only output if entered as free text. |
| Product: Surveillance | 29297132, 30019603, 30379636, 30537501, 30588885 | Test report is not accepted when a supplier action is required
This issue occurred due to there being no Product Technologist associated with the product record and, in the case of Produce product records, there was a missing link. When accepting a test report, which requires supplier action, a Product Technologist must be associated against the product record to allow for an email to be sent. A fix has been implemented and addresses the following:
|
| Project: Glossaries | 30543175 | Duplicated codes in Project glossaries
A fix has been made to rectify an issue with the duplication of the unique id codes that are assigned automatically when creating new Project glossary records in the Admin area. The records affected were Project Templates, Activity Templates, Brief Templates, and Activity Types. Validation assures the codes are unique. Note: In existing installations, a data update script will run as part of the upgrade, automatically correcting any existing duplicates. However, a system administrator (with ORACLE AUTHORIZED ADMINISTRATOR access rights) may wish to check for any duplicates prior to the upgrade and correct them by editing and updating the Code. |
| Project: Hierarchy View | 27124167, 30811604, 30826309 | Error when opening Projects in Hierarchy All and Hierarchy views
A fix has been made to rectify an error when attempting to open a project from the Hierarchy list view. The error occurred due to the activity sub-status description in the list view not being initialized. |
| Project: Linking | 28918955, 30214332, 30537260 | Unable to open linked Project from Product Record
A fix has been made to rectify an issue where it was not possible to open a Project that was liked to a Product Record when attempting to do so from the embedded list view in the Project Links page. The issue was due to an inconsistency between the formatting of the CSS links and the actual record access. |
| Project: Linking | 29452966 | Issue with linking of Projects to Product Records and Specifications
A fix has been made to rectify an issue with the linking of Product Records and Product Specification to Projects. The issue occurred when no site had been specified; the linking was selecting projects which matched the supplier, but which also had a site. |
| Project: Project Details | 29800576 | Incorrect Product information for Site users
A fix has been made to rectify an issue where incorrect Project information was presented to Site users. The issue resulted in users who are assigned to specific sites of a supplier having visibility of Projects associated with other sites (of the same supplier). |
| Reports: BI Publisher Reporting | 29117537, 29123963, 29515066, 30650432 | Issues with Excel report outputs
A fix has been made to address issues with the Excel report output type, generated by BI Publisher. The fix makes a new MS Excel (XLSX) option available as an output type when scheduling a report. Using this option instead of the current MS Excel (XLS) option avoids the following issues:
Any existing reports with these issues can be rescheduled, with the output type being changed to MS Excel (XLSX). |
| Reports: BI Publisher Reporting (CR40) | 30837266 | CR40: Division missing from Product Coverage data
A fix has been made to the Produce Specification Acceptance report (ref. CR40) to rectify an issue with Division being missing from the products covered data. The fix is to reference Product Specification rather than the Product Record as the primary source of the product coverage data. |
| Reports: Legacy Reporting | 29590339 | Custom fields missing from CNF Specification reports
A fix has been made to legacy reports to include Custom fields in the Product report domain for Constructed Non Food product specifications. The fields relate to the Batch Coding custom fields. Note this may be known as the Coding, Traceability and Other Requirements / Additional Questions in some portals. |
| Reports: Legacy Reporting | 29911106, 30888215 | Attachment Reports have characters missing
A fix has been made to rectify an issue with missing characters in legacy Attachment reports. The issue occurred for languages containing special characters, such as Chinese and Japanese, resulting in characters missing from the attachment description. The fix enables legacy reporting to output the descriptions for all locales that have been installed on the reporting system. For any cases where more than one description language has been entered for a single attachment, the report will present the descriptions on separate lines on the same row. The descriptions will appear on the same line in the Reports module UI, due to the way it displays line breaks. |
| Supplier: Contacts | 29519790 | Mandatory Contacts required when deactivating a Site
A fix has been made to rectify an issue with the validation of Supplier and Site mandatory contacts. The validation for contacts having been assigned to the mandatory contact roles was being applied when progressing a site to an inactive, unapproved, or delisted status. As the contacts are not relevant at these statuses, the mandatory contact validation has been suppressed for such status changes. |
The following post release tasks must be taken into account as part of this release:
If the Nutri-Score feature is to be used, the following change should be made in the Permissions spreadsheet, to provide access to the new administration options.
Add the following rows to the Admin page:
| Record | Authority Profile | Menu Option | Sub Menu Option | Action | Data Record | User Mode | Access Level | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Admin | Product Administrator | Admin | NUTRI SCORE CATEGORY | NORMAL | Y | |||||||
| Admin | Product Administrator | NUTRI SCORE CATEGORY | NORMAL | F | ||||||||
| Admin | Product Administrator | SET TO ACTIVE | NUTRI SCORE CATEGORY | NORMAL | Y | |||||||
| Admin | Product Administrator | SET TO INACTIVE | NUTRI SCORE CATEGORY | NORMAL | Y | |||||||
| Admin | Product Administrator | NEW VERSION | NUTRI SCORE CATEGORY | NORMAL | Y | |||||||
| Admin | Product Administrator | NUTRI SCORE BASELINE DETAIL | NORMAL | F | ||||||||
| Admin | Product Administrator | NUTRI SCORE BASELINE ROW | NORMAL | F | ||||||||
| Admin | Product Administrator | NUTRI SCORE MODIFYING DETAIL | NORMAL | F | ||||||||
| Admin | Product Administrator | NUTRI SCORE MODIFYING ROW | NORMAL | F | ||||||||
| Admin | Product Administrator | NUTRI SCORE MODIFYING CONDITION ROW | NORMAL | F | ||||||||
| Admin | Product Administrator | NUTRI SCORE SCORE | NORMAL | F | ||||||||
| Admin | Product Administrator | Admin | NUTRI SCORE SCORE | NORMAL | Y | |||||||
| Admin | Product Administrator | NUTRI SCORE SCORE DETAIL | NORMAL | F |
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.
Enable the Nutri-Score feature for Food and/or Produce specification types, and set whether the scores are to be included on pack, by setting the system parameters.
Configure the Nutri-Score Categories for the different types of product that are to have scores calculated, and define the associated points/score conversion rules. Also configure the corresponding Nutri-Score Scores glossary as required.
The Nutri-Score data appears in the specification's Nutrition section, the Pack Copy file (if configured), the API XML payload, data extract, and the Reports data source.
Existing and new specifications will show the Nutri-Score field set if the feature is enabled.
As part of the enhancement, the order of the columns in the Nutrition panel outputs for all legislations become controlled by the order set in the Available Columns table of the Nutrition Panel glossary record. Check that all existing Nutrition Panels are configured as required.
Log in to the application as an administrator with the Oracle Authorized User role.
Navigate to Company > Admin > Products.
Expand Spec Glossaries > Food > Nutrition and choose Nutrition Panels.
Click on the Active category to get a list of the potential Nutrition Panels that may need correcting.
Open each record in turn and determine if the rows in the Available Columns table are in the correct order:
Per 100 g/ml
Per Serving
%Reference Intake Per 100 g/ml
%Reference Intake Per Serving
Reference Intake
If the rows are determined to not be in the correct order, follow these steps:
Choose Action > Edit.
Choose Action > Create New Version.
On the Available Columns table, use the Add/Remove Columns button to remove all values from the table. Note: You may have to do this several times in order to empty the table.
Add the rows back into the table noting to select the appropriate Present by Default value.
Check the change history to ensure that only these changes have been flagged as a change.
Choose Action > Activate.
Choose Action > Save & Exit.
After saving, reopen the new record and check the change history. An additional entry for the Status change should be recorded.
Repeat for each record until all are processed.
Repeat the above steps for the BWS and Produce specification types.
Configure any Nutrition Panels that are required to make use of the new dual nutrition (As Sold and As Prepared) column declaration. The necessary options appear in the Nutrition Panel and Front of Pack Product Type glossaries for the supported legislations.
The Dual Panel format declaration output appears in the specification's Nutrition section, the Pack Copy file, the API XML payload, data extract, and the Reports data source.
Existing and new specifications will show the As Prepared fields in the Nutrition section header if a panel with the As Prepared Values option is selected.
The nutrition panel declaration outputs for all legislations will now be generated as a simple table, with all graphical formatting removed.
The simple panel formatting will be applied to all new Specifications and to any existing Specifications when the nutrition declaration is recalculated (existing specifications at Pack Copy Sent status, or beyond will continue to display the old rendering, unless recalculated).
The Dual Panel format only applies to tabular type panels. There is no change to linear type panels, which continue to only show As Sold values (but with any graphical formatting removed).
New reports become available. Configure a schedule for those required to be run.
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:
Ensure the MYARTWORK external system has been created in Brand Compliance PROD and STAGE.
Raise an SR service request for creation of the Artwork application for PROD and STAGE. The call back URLs and IDCS URLs must be provided in the SR.
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.
For more information, see the following documents in the Oracle Retail Brand Compliance Management Cloud Service Release 18.3 documentation set:
Oracle Retail Brand Compliance Management Cloud Service Administration Guide
Oracle Retail Brand Compliance Management Cloud Service Implementation Guide
Oracle Retail Brand Compliance Management Cloud Service User Guide
Oracle Retail Brand Compliance Management Cloud Service Product User Guide
Oracle Retail Brand Compliance Management Cloud Service Project User Guide
Oracle Retail Brand Compliance Management Cloud Service Reports User Guide
Oracle Retail Brand Compliance Management Cloud Service Supplier User Guide
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Retail Brand Compliance Management Cloud Service Release Notes, Release 18.3
F26784-03
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.
Value-Added Reseller (VAR) Language
Oracle Retail VAR Applications
The following restrictions and provisions only apply to the programs referred to in this section and licensed to you. You acknowledge that the programs may contain third party software (VAR applications) licensed to Oracle. Depending upon your product and its version number, the VAR applications may include:
(i) the MicroStrategy Components developed and licensed by MicroStrategy Services Corporation (MicroStrategy) of McLean, Virginia to Oracle and imbedded in the MicroStrategy for Oracle Retail Data Warehouse and MicroStrategy for Oracle Retail Planning & Optimization applications.
(ii) the Wavelink component developed and licensed by Wavelink Corporation (Wavelink) of Kirkland, Washington, to Oracle and imbedded in Oracle Retail Mobile Store Inventory Management.
(iii) the software component known as Access Via™ licensed by Access Via of Seattle, Washington, and imbedded in Oracle Retail Signs and Oracle Retail Labels and Tags.
(iv) the software component known as Adobe Flex™ licensed by Adobe Systems Incorporated of San Jose, California, and imbedded in Oracle Retail Promotion Planning & Optimization application.
You acknowledge and confirm that Oracle grants you use of only the object code of the VAR Applications. Oracle will not deliver source code to the VAR Applications to you. Notwithstanding any other term or condition of the agreement and this ordering document, you shall not cause or permit alteration of any VAR Applications. For purposes of this section, "alteration" refers to all alterations, translations, upgrades, enhancements, customizations or modifications of all or any portion of the VAR Applications including all reconfigurations, reassembly or reverse assembly, re-engineering or reverse engineering and recompilations or reverse compilations of the VAR Applications or any derivatives of the VAR Applications. You acknowledge that it shall be a breach of the agreement to utilize the relationship, and/or confidential information of the VAR Applications for purposes of competitive discovery.
The VAR Applications contain trade secrets of Oracle and Oracle's licensors and Customer shall not attempt, cause, or permit the alteration, decompilation, reverse engineering, disassembly or other reduction of the VAR Applications to a human perceivable form. Oracle reserves the right to replace, with functional equivalent software, any of the VAR Applications in future releases of the applicable program.
