3 Noteworthy Resolved Issues
This following table 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: Email Notifications |
33624924, 33693406, 33581743 |
Duplicate notification emails A fix has been made to rectify an issue with notification emails being sent multiple times. The issue relates to the following batch jobs, which were running on multiple servers, and were therefore issuing duplicate notifications:
The batch jobs now run just once, regardless of the number of servers. |
|
General: Global Network Bus |
29507463 |
Enhancement to validate that a satellite record is enabled before failure record re-submitted To prevent a loss of data due to data not being successfully synced, a new validation check has been introduced. When Re-submit Synchronisation is selected where a satellite record is disabled, an error will be generated: Re-submission is not possible because the Satellite is disabled. |
|
General: Global Network Bus |
32392153, 29793880 |
Global Network Bus intermittently not displaying failure messages Failure messages which contain characters which are invalid in XML such as the ‘&’ result in no failure messages being displayed. An update to manage these characters has been implemented so General Network Bus (GNB) failure messages are always displayed. |
|
General: Global Network Bus |
32661927, 33556264, 33331064 |
Error occurs on product specification sync process via the GNB The product specification sync process fails when it attempts to create a new product covered record instead of updating an existing one. This issue generated a duplicate key error. An update to the Product REST API resolved the underlying issue in identifying an existing product covered record to update. |
|
General: Global Network Bus |
32662027, 32750531 |
Failure when creating new multi-pack specification during synchronizing of Product Specifications During the synchronizing of Product Specifications, a failure was identified when creating a new multi-pack specification. An internal change has been made to resolve the issue. The change does not affect the Product Specification API. |
|
General: User API |
33319402 |
Enhancement to the User REST API The User REST API has been enhanced to include the <restrictedAuditorAccess> XML TAG, which corresponds to the "Restricted Auditor Access" flag that is available for Retailer Users. |
|
General: System Text |
31693367, 33281390, 34006657, 33326032, 33343345 |
Help Text not available for some fields on Product Specifications Help text was not appearing against fields where the key (system text Code field) for labelling fields did not follow standard conventions. This was identified for, but not limited to, the Product Specification fields:
An update has been implemented to ensure the help text is presented for all fields. |
|
General: User Login |
33454275, 33903749, 33722501, 33793407 |
Users unable to log on to ORBCM system An issue occurred after a system restart whereby users were unable to log on to the ORBCM system, due to a cache issue. An update has been made to prevent the cache issue occurring which will prevent the login error. |
|
Products: API |
32889620 |
Update of Product records using the Product Record REST API results in an error An issue was identified with updating existing Product records using the Product REST API when the records have existing Shipping Case Code data. A code change to the Product REST API to successfully process the update of Products which contain Shipping Case Code information has been implemented. |
|
Project: Activities |
33487331 |
Update to the Activity Sub Status intermittently caused an error An update has been implemented so that Activity records can now be successfully saved after editing the Sub Status. |
|
Reports: Advanced Packaging |
33246837 |
Tamper Evident field not available in the Advanced Packaging Component query for reporting on The Tamper Evident field was identified as not being available for reporting on, under the Advanced Packaging Component query. The query has now been updated, to include the Tamper Evident field. A new system text entry is available for managing the query column name. See Post Release Tasks for further details. |
|
Reports: Advanced Packaging |
33410610, 33895252 |
Advanced Packaging reports do not include Produce specification types The Advanced Packaging queries do not provide Advanced Packaging data for Produce specifications. Updated queries now include the data for the Produce specification type, for the following queries:
|
|
Reports: Allergen |
33608625 |
Information associated with Natasha’s Law is not available for Reporting on Updates were made to the following queries to ensure the inclusion of Other Allergen Declarations and Declaration fields:
|
|
Reports: Audits |
33544252 |
Audit query provides unexpected data The Audit query produced the wrong data for the Issue Changed By and Issue Created By fields. The query has been updated so the fields are now populated with the correct data. |
|
Reports: Nutrients |
33521666, 33485431 |
Nutrient queries missing a required field for reporting on The Serving Size field was missing from the Nutrient queries:
An update to the queries to include the field has been implemented. |
|
Reports: Nutrition |
33516850 |
Energy calculation update for India Nutrition Labelling requirement Due to a legislation change, an update was required to the Energy calculation for India Nutrition Labelling. The change is to the polyols multiplier, going from 2.4/10 to 2/8 for kcal/kj respectively. |
|
Reports: Products |
33378451, 33410327 |
Spec Type field not available in the Product query for reporting on The Spec Type field was identified as not being available for reporting on under the Product query. The query has now been updated to include the Spec Type field. A new system text entry is available for managing the query column name. See Post Release Tasks for further details. |
|
Reports: Product Shelf Life |
33503861 |
Pack Coding query is missing a field An update to the Pack Coding query has been implemented to include the Period field. A new system text entry is available for managing the query column name. See Post Release Tasks for further details. |
|
Reports: Product Specification |
32949597, 32844324, 33030981 |
Specification History fields required for Reporting on are not available Specification History information is required in certain queries to identify the reason work is being carried out on a new version of a spec. The following fields from the Specification History table (Specification Main Details) were identified for reporting:
The data is concatenated where there is more than one row in the Specification History table for the given specification. These fields are now included in the following queries:
|
|
Reports: Scheduling |
33603668 |
Report Scheduling does not give the schedule creator access to generated reports Previously, a user’s details needed to be included in the Recipients for the scheduling record to access any report output for the schedule. An update has been implemented so a user who creates a report scheduler record will automatically have access to the reports produced. |
|
Supplier: Audits & Visits |
33265075, 33190648 |
Overdue email notifications not being sent to Retailer users Overdue email notifications were only sent to Retailer users if the system parameter Send Audit/Visit Due Notifications to Retailer was set to Yes as well as the required Send Audit/Visit Overdue Notifications to Retailer. An update now ensures overdue email notifications to retailers is only reliant upon the Send Audit/Visit Overdue Notifications to Retailer system parameter. |