SCM release notes v2.22.x
Solution | Supply Chain Monitoring |
Version | 2.22.4 |
Type of release | Patch |
Live release date | 18 November 2022 |
Improvements and bug fixes
Fixed a mismatch in the temperature alarm email text.
Solution | Supply Chain Monitoring |
Version | 2.22.3 |
Type of release | Patch |
Live release date | 18 October 2022 |
Improvements and bug fixes
Updating “continued alarm” emails to reflect emails for temperature alarms.
Bug fix: Edge case were there was an DNS issue causing users to be unable to login in certain situations.
Solution | Supply Chain Monitoring |
Version | 2.22.2 |
Type of release | Patch |
Live release date | 7 October 2022 |
Improvements and bug fixes
Updating db parameters for shipment search by custom properties to reduce db load and improve performance.
Solution | Supply Chain Monitoring |
Version | 2.22.1 |
Type of release | Patch |
Live release date | 28 September 2022 |
Improvements and bug fixes
Blocking users from delivering a single logger if there is no shipping time.
Improved error handling in backend components.
Minor bug fixes related to 3pd devices.
Solution | Supply Chain Monitoring |
Version | 2.22.0 |
Type of release | Minor |
Release announcement date | 9 August 2022 |
Live release date | 27 September 2022 |
In this release we are taking the first step towards providing 3rd party device support.
New features
The minimum and maximum temperature values are one of the first data points that Quality Release look at when determining if a product can be released to market.
This information has been available in the pdf shipment reports that are generated at the end of the shipments, but is now available in the UI from the time logger starts reporting after the shipment is started.
SCMRS-555 | User can see the minimum and maximum recorded temperature values across all loggers in the shipment detail view. |
This information will be available to all users with access to the shipment. No change in how the system is used. This additional information can be leverage as needed by the users.
We made minor updates with regards to how logger excursion events are displayed if a shipment is manually delivered to a time prior to the excursion taking place. This changed is aimed to reduce possible confusion for users and improve consistency of how the data is presented in the user interface.
In the example, the logger was removed from the product, but the shipment wasn’t delivered. The temperature increased, resulting in an excursion. The shipment is later manually delivered at the time when the logger was detached from the product. This leaves the excursion, as shown in the image above, outside the monitoring period.
Previously, SCM was accounting for all excursions reported from loggers paired with the shipment and showing the excursions as triggered (see below image). This has been causing confusion for shipments similar to the example above.
The Excursion Boundaries table will now only show excursions that happened within the monitoring time resulting in the table being displayed as below.
In the process of duplicating shipments, it was identified that it needed to be made more clear to the user if a logger in the shipment was inactive (recalled or disabled).
Two steps were added:
First, there is an error message in the pop-up modal notifying the user that a logger in the shipment that is being duplicated is inactive.
Second, after the shipment is duplicated there will be an empty logger slot for the disabled logger. This ensures that the shipment is not completed without addressing the empty logger slot.
A warning was added to ensure that users that are requesting a report manually identify if the shipment is missing data before going ahead and requesting the report to be sent to an email address.
Controlant is taking the first step to support data from 3rd party devices. At first, the support will be limited to a specific provider and a specific device for a defined project.
The bulk of the changes will be outside the SCM solution but a couple of changes needed to be made for the SCM solution to ensure expected functionality.
SCMRS-551 | SCM will not allow users to manually create new shipments with 3rd party devices. |
SCMRS-552 | SCM will not allow users to duplicate shipments with 3rd party devices through SCM UI. |
SCMRS-553 | SCM will not allow users to add 3rd party devices to existing draft shipments through SCM UI. |
SCMRS-554 | The system will consider it to be a missing data point if the time period between two measurements is more than the sampling rate plus 30 seconds. |
SCM will accept and be able to handle data from 3rd party devices. For most users there is no impact.