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 Supplier Evaluation 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.

Table 1-1 Noteworthy Enhancements

Feature	Module Impacted	Scale	Delivered	Customer Action Required?
Additional Languages	All	Small	Yes	Yes Apply any translation overrides.
OAuth Enablement	Application Program Interfaces (APIs)	Medium	Yes	No
Site Reference Notifications	Supplier	Medium	Yes	Yes
Supplier and Site Deletion	Supplier	Medium	Yes	Yes
Audit Outcome Summary Report	Reports	Medium	Yes	Yes
Assignments Description in Business Language	Workspace	Small	Yes	No
REST API Attachments	Application Program Interfaces (APIs)	Medium	Yes	Yes

Additional Languages

The following languages have been introduced:

Arabic
Chinese-Traditional
Croatian
Greek
Hungarian
Korean
Polish
Turkish

The languages are available now as active languages, for full translation to be provided in the future. If any of the new languages are not required, the Language record should be deactivated. See Post Release Tasks.

OAuth Enablement

As part of the move to the Next Generation Cloud environment, there is change in the way clients authenticate with the application when using the APIs.

The current basic authentication method requires that for each call to the application a username and password be supplied in order to authenticate with the application before being allowed to call the API. This approach means that for each call to an API, traffic has to be routed through to Identity Management to verify and authenticate the username and password before being allowed to actually call the API, thus putting unnecessary load onto the Identity Management environment as well as the networking layers of the infrastructure.

The approach for the Next Generation Cloud is a move to OAuth authentication (which is enabled when the environment is built). OAuth allows a token to be generated by Identity Management when an API is called for the first time, then subsequent calls to the API can pass this token so that the APIs can simply be called without having to return to IDCS. The token lasts for a period of time, after which a new token must be obtained.

This requires clients to change their implementation and use of the Supplier Evaluation APIs, to utilize OAuth.

Site Reference Notifications

The References page of the Site record contains a table for recording the site’s certification details, such as EC Licence Number, Organic or Kosher Certification. Each reference/certification may optionally hold an expiry date.

The enhancement introduces an automated notification to advise the appropriate users when a site’s reference/certification is becoming due or has expired. The notification is in the form of an email and/or an assignment task to the site’s lead technologist, and designated supplier contacts. The feature includes a new batch job, system parameters, email templates, and tasks/assignments.

Use of the notification and the rules for its generation are all configurable. The feature is disabled by default, requiring the client to enable and configure it for use. See Post Release Tasks for details of the configuration requirements.

New Assignments/Tasks

Assignment Type	Source	Visible To	Target
Sites with References Due {0}	Shown if any associated sites have references/certificates becoming due	Retailer users who are designated Lead Technologist for the Site Supplier users with the designated contact roles for the Site	Sites with References Due list view.
Sites with References Expired {0}	Shown if any associated sites have references/certificates that have expired	Retailer users who are designated Lead Technologist for the Site Supplier users with the designated contact roles for the Site	Sites with References Expired list view.

Assignment Type

Source

Visible To

Target

Sites with References Due {0}

Shown if any associated sites have references/certificates becoming due

Retailer users who are designated Lead Technologist for the Site

Supplier users with the designated contact roles for the Site

Sites with References Due list view.

Sites with References Expired {0}

Shown if any associated sites have references/certificates that have expired

Retailer users who are designated Lead Technologist for the Site

Supplier users with the designated contact roles for the Site

Sites with References Expired list view.

New Email Templates

Trigger	The Site Reference Expiry Notifications batch job identifies a site's certificate/reference as becoming due.
Email Code	SITREFDUE
Email Description	Notification that a site has a certificate/reference becoming due.
Content	From: [Portal Name] Sent: [Date & Time] To: See Recipients below Subject: This site has a reference certificate that is due within the next [Days] days Site: [Site Name], Site Number: [Site Number] #if ($showInternationalNames ) ([sitelocalname]) #end This is an email automatically generated by the <Portal Name> Portal, please contact $supportemail if you require assistance or believe this message has been sent to you in error.
Recipients	Based on the Site Reference Notification system parameters: If Notify Lead Technologist by Email is checked, the site's Lead Technologist retailer user. If Notify Supplier/Site Contacts by Email has roles specified, supplier users associated with the site who have the designated roles. User's accounts must have Login ID Disabled unchecked.
Sensitive	No

Trigger	The Site Reference Expiry Notifications batch job identifies a site's certificate/reference as being expired.
Email Code	SITREFEXP
Email Description	Notification that a site has a certificate/reference that has expired.
Content	From: [Portal Name] Sent: [Date & Time] To: See Recipients below Subject: This site has a site reference certificate that has expired. The [Reference Type] reference type has an expiry date of [Expiry Date] for Site: [Site Name], Site Number: [Site Number] #if ($showInternationalNames ) ([sitelocalname]) #end This is an email automatically generated by the <Portal Name> Portal, please contact $supportemail if you require assistance or believe this message has been sent to you in error.
Recipients	Based on the Site Reference Notification system parameters: If Notify Lead Technologist by Email is checked, the site's Lead Technologist retailer user. If Notify Supplier/Site Contacts by Email has roles specified, supplier users associated with the site who have the designated roles. User's accounts must have Login ID Disabled unchecked.
Sensitive	No

Supplier and Site Deletion

The existing facility for deletion of Supplier and Site accounts is intended as a post on-boarding facility for removing accounts that are not used, so is restricted to only allowing sites to be deleted if they have no associated contacts, users, or other types of records.

The enhancement provides more deletion capability, by the use of soft deletion of Supplier and Site records, and removal of associated Contacts, Users and references in Alerts, Documents, and Announcements/News Items. However, deletion is not permitted if the account has other types of records associated to it, such as Audits, Assessments, or links to Processes.

The deletion facility is restricted to only users with Power Administrator access rights. The feature is a change to the existing supplier and site deletion facility, so the enhancement functionality becomes available automatically, but requires a Permissions configuration change to enable it. See Post Release Tasks.

Note:

There is a known issue with the behavior of the Supplier list view, where associated Sites that have been soft-deleted remain visible within the Site Name and Site Code columns. The current list views architecture only permits filtering of deleted records for the main entity being listed (in this case the Supplier record). This constraint will be taken into account when designing the equivalent list view for the new JET UI, with the aim being that deleted Site records are filtered out of the Suppliers list view.

Audit Outcome Summary Report

The new Audit Outcome Summary report (CR110) is a form style report. The user applies filters in the report schedule to identify a specific Audit (or limited number of Audits) to be included in the report.

The report uses a new Audit Outcome API data source, which is based on the Audits API data source plus a number of additional fields from the Audit's associated Site record (Status, Type, GLN, Top Grade, Business Unit, Business Categories, Technologists, and Custom Fields), as well as from the Contacts (Name, Email, Roles, and Phone). The report provides totals of the Audit’s issues/non-conformances (open issues, overdue issues, and total issues).

For the tables of the site’s Contacts, in order to filter for specific contact roles, the filters must be applied to the report’s RTF template file. These filters cannot be applied to the report design or schedule because the data source is an API. See Post Release Tasks.

See the Oracle Retail Supplier Evaluation Cloud Service Report Layouts document for details of the report contents, and the Oracle Retail Supplier Evaluation Cloud Service Reports User Guide for guidance on applying filters within the RTF template.

Assignments Description in Business Language

The Description column in the Assignments list view identifies the type of assignment, typically by the name of the record. Some records may hold a corresponding description in the portal’s business language. The Description in the Business Language column is now available to be added to the Assignments list view.

REST API Attachments

The existing facility for retrieving files attached to certain types of record through the REST APIs is extended to make the facility available to all main record types.

The following REST APIs now allow for the retrieval of the attachment ids, and subsequent retrieval of the actual attachment files by calling the Attachment REST API:

Users
Suppliers
Sites
Audits
Audit Issues/Non Conformances
Assignments/Scorecards
Processes/Projects
Process/Project Activities

To utilize this facility, the client must develop the necessary web services to call the Supplier Evaluation APIs. See Post Release Tasks.

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.

Additional Languages

The Additional Languages feature introduces eight new languages. If any are not required, the Language record should be deactivated, within the System Text section of the Admin area.

Site Reference Notifications

If the Site Reference Notifications feature is to be used, the following administration tasks are required to enable and configure it:

Configure the system parameters in the Registration page of the System Parameters record in the Admin area according to the required behavior:
- Generate Reference Due Emails enables email notifications for site references when they become due.
- Becomes due prior to expiry date (days) determines when a site reference becomes due (the number of days prior to the expiry date).
- Re-send Reference Due email frequency (days) controls the frequency of the Reference Due email (the number of days since it was previously sent).
- Generate Reference Due Assignments enables assignment task notifications for site references when they become due.
- Generate Reference Expired Emails enables email notifications for site references when they expire.
- Re-send Reference Expired email frequency (days) controls the frequency of the Reference Expired email (the number of days since it was previously sent).
- Generate Reference Expired Assignments enables assignment task notifications for site references when they expire.
- Notify if Site Status controls which site statuses are to have site reference notifications. The default is Active and Awaiting Approval.
- Notify Lead Technologist by Email controls whether the site's lead technologist is to be a recipient of site reference email notifications.
- Notify Lead Technologist by Assignment controls whether the site's lead technologist is to be a recipient of site reference assignment notifications.
- Notify Supplier/Site Contacts by Email is a picklist of the mandatory contact roles, used to determine the supplier recipients of site reference email notifications.
- Notify Supplier/Site Contacts by Assignment is a picklist of the mandatory contact roles, used to determine the supplier recipients of site reference assignment notifications.
Make any custom overrides to the new system text, and email templates:
- Notification that a site has a certificate/reference becoming due (SITREFDUE).
- Notification that a site has a certificate/reference that has expired (SITREFEXP).

Supplier and Site Deletion

The following administration tasks are required for the Supplier and Site Deletion enhancement.

A Permissions change is required to enable the facility. Add the following to the Site tab of the Permissions spreadsheet.

Record (A)	Authority Profile (B)	Menu Option (C)	Sub Menu Option (D)	Action (E)	Data Record (F)	User Mode (L)	Access Level (M)
Site	POWER ADMINISTRATOR			DELETE MANUFACTURER	Site	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.

The soft deleted records are excluded from list views and data extracts. To exclude the soft deleted records from reports, it is necessary to add the Deleted column as a filter to the relevant Report Data Source, Report Design, and Report Schedule records.
By default, soft deleted records are returned by the APIs (the XML contains a deleted element, which is set to true). To exclude soft deleted records, it is necessary to use a softDelete=false parameter when calling the API. For example:
```
/creations-core/services/rest/site?softDelete=false
```

Audit Outcome Summary Report

The following administration tasks are required if the new Audit Outcome Summary report is required to be run:

To filter for specific contact roles to be included in the report, create a custom version of the report’s RTF template file (CR110_Audit_Outcome_Summary.rtf) and add the appropriate filtering. These filters cannot be applied to the report design or schedule because the data source is an API.
Make any custom overrides to the new report layout or system text.
Schedule the report to run, as required.

ReST API Attachments

To utilize the facility for retrieving file attachments using the APIs, the client must develop the necessary processes to call the Supplier Evaluation APIs. See the AttachmentsRestService section in the Oracle Retail Supplier Evaluation Cloud Service Implementation Guide for further details.

In order to access the Supplier Evaluation APIs, the necessary External System records must be configured by the system administrator.

Permissions

For the change to permit retailer users to edit the Growers List in the Site record (item 31450870), assign the Supplier & Site Administrator authority profile to any users who require that level of access.

List View Configuration

For the changes to the Contact information in the Supplier list views (items 33709195 and 34446591), any existing Supplier list views that reference the Fax and Phone columns need to be modified in order to use the corrected fields. Remove those columns from the list view, and then re-add them and save, as appropriate.

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 Supplier Evaluation 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 Supplier Evaluation 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 Supplier Evaluation 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 Supplier Evaluation Cloud Service Administration Guide for the full process for enabling Artwork with SSO.