SCM release notes v2.23.x

Adding partitions to database schemas.

Database schema updates to prevent primary key overflow issues.

Bug fix: Exclude IgnorePeriod in the evaluation of shipment measurement aggregations (min, max).

Adding a warning step when a user transitions a Ready shipment to Shipping if the shipment does not have any temperature boundaries. This is to reduce the risk of unintended shipments with no temperature warnings applied.

Bug fixes for the create shipment flow.

Fixing a bug where excursion notifications were not sent out if the shipment reference contained illegal characters. The characters that are now handled in addition are:

Fixing a bug where excursion notifications were not sent out if the shipment reference contained illegal characters. The characters that are now handled in addition are:

Make sure “+” characters can be searched for in the Search tab.

Passing date range for users in “+UTC” properly in the Search tab.

Fixing the issue where a disabled contact in a Contacts Template could make other contacts not appear when the template was used in a shipment.

Fixing errors when creating a Shipment Template with a disabled contact in the Template.

Making sure the template name stays with the Shipment after editing and adding custom properties in a Draft Shipment.

Making sure custom boundaries added in addition to a shipment created with templates stay after editing the draft and saving.

Fixing issue with Shipment Templates with “Allow Users to Choose” losing manually entered boundaries.

Adding a warning in the Ready Shipment modal to alert the user that boundaries are missing from the shipment.

Fixing Fahrenheit conversion when using Shipment Templates where the user is set to Fahrenheit.

Making sure that a warning step can appear if a user is set to Fahrenheit and using a template with “Allow users to Choose”.

For manually created shipments, if the user decided not to select draft in the beginning screen, but instead selected a Shipment Template with boundaries, filled the information, and then clicked “Save as Draft”, then the boundaries could have gotten removed from the shipment.

Similar case, if the user went through the same flow, selected a Warning Template and then “Save as Draft”.

Creating the shipment normally was not affected, nor if the user selected the draft checkbox in the beginning.

Fixing issue with custom properties in draft shipment.

Allowing users with certain security scans to click on password reset links without errors.

Fixing the monitoring lines showing right away when a chart is opened.

Improving the session timeout handling

Fixing a bug in the single logger view that was causing not all logger events to show for the selected time interval.

Fixing a bug where an email entered for request report was not clearing when a user requesting to send a new report.

Text trim added to search input fields to allow users to enter blank space before and after text without impacting the search results.

Fixing the interval used for missing data analysis to be inclusive of the monitoring start and monitoring end timestamps.

Fixing the Logger scanner functionality to keep the value of the logger visible even after a second one is scanned in.

Fixing dual boundary validation when manually adding logger to a shipment through a scan and checking the logger firmware version.

Bug fixes:

Styling improvements.