| Page Properties | ||||
|---|---|---|---|---|
|
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
SCM v2.2526.0 is the 2023 quarter 2 3 release. The planned release date is 22 Jun and the functionality will be available on the UAT testing environment from 25 May .
In this release we are introducing our new Audit Trail, launching Delivery Automation, and improving the investigative UX flow of our shipments by exposing the worst-performing logger temperature data in our shipment view. In addition, we are providing better feedback to our users when loggers are missing or pending data in our shipments.
Audit Trail
Description: The Audit Trail is part of the system that receives information about changes from other internal systems and stores them as audit records. The new audit trail solution has an updated user interface (UI) that is more user-friendly and helps the user find the audit record they are looking for quicker and more efficiently.
The previous Audit Trail view is still opened directly from the Audit Trails option in the left-side navigation menu of Account Admin. The new UI for Audit Trail is accessible via a link in a banner at the top of the page in the previous Audit Trail UI.
...
Once opening the new Audit Trail UI for the first time, users are presented with a table of Audit Records that can be filtered by user, date, category, or Reference/ID. There’s an empty information section on the right-hand side that gets populated with information about an audit record. A link above the table filters allows users to navigate back to the previous Audit Trail UI.
...
Once an audit record has been selected, the right-side information section gets populated with the relevant data, as can be seen in the picture below. The user can also press “View Details” in the bottom right corner of the screen after selecting an Audit Record from the table. This navigates them to the Record Details screen, where they can see the Metadata, a Data Snapshot, and all of the changes associated with the Audit Record. The Changes are displayed in a 3-column table with the name of the changed value, the original value, and the updated value. The Data Snapshot is a JSON viewer where the request that created the Audit Record can be viewed in its entirety. It is also possible for the user to download the JSON file from the Data Snapshot by clicking the highlighted button from the screenshot below.
...
Delivery Automation
Description: With this release, we are adding three additional criteria for the automatic delivery of loggers and performing logger delivery as an opt-in feature for customers.
Delivery automation is intended to capture “out-of-flow” scenarios, e.g., when a user doesn’t press the stop button, there is poor connectivity, or manual upload is required. The delivery automation stops the monitoring automatically at the correct time, which leads to the faster generation of the shipment summary report. It also reduces the risk of “false excursion” after the logger has been removed from the shipment.
Time out of bounds, Min and Max temperature of a logger are visible within the shipment
Description: The total time out of bounds, Min and Max temperature of a logger was added to the boundaries table. The aim is to improve the user experience (UX) while users are investigating issues with excursions and to make the information found in the pdf reports consistent with the UI.
On a delivered shipment*, when a boundary is expanded, the data for Time out of bounds and Min and Max temperature is shown for each logger. The highest time and highest/lowest temperature are also highlighted to quickly identify the worst-performing loggers.
...
Values for Time out of bounds, Min and Max temperature are only available AFTER delivery and data analysis of each shipment. While the shipment is shipping, those values are not shown.
...
Also worth noting is that the UI design has been updated to better reflect modern patterns and better delineate the data between different boundaries.
Before
...
After
...
An important note on this update:
Notification boundaries will not display this value as we are not currently storing this information because it is not Quality impacting. We will be fixing this in an upcoming patch but want to inform our users to minimize confusion.
This has no impact on the system’s ability to send an alarm if an excursion is triggered or on Quality assessment functionality.
Rearm UI adjustments
Description: With redesigning the boundaries table, the rearm UI has been slightly adjusted as well, following feedback from our heavier users. The rearm checkbox is now next to the boundaries, so that users don't have to expand each row to select the loggers. The rearm all functionality is now a checkbox above all the other checkboxes to better follow standard UI patterns.
...
Light event and Manual Data Upload visible in the Logger events list
Description: We have added light and Manual Data Upload events to the logger events list to help our users better investigate shipments on a logger level.
...
The Inspection Comment character limit increased to 2000
...
Missing Data UI Improvements
Description: We have received feedback regarding missing data and decided to improve the flow by giving users better feedback concerning any issue coming up during shipments.
To better describe the term of the status “Missing data” will be changed to “Pending data” and a tooltip will be added to explain the Shipment Analysis Section better.
...
In the Logger section, the next logger wake-up time (when the logger is scheduled to send data) will be displayed to help users know if the pending data is due to normal circumstances or an issue with the logger battery or connectivity that needs manual intervention.
If a wake-up interval goes overdue AND there is missing data, a tooltip will appear to give users more direction on possible fixes.
...
If a wake-up interview is NOT overdue, but there is missing data on the logger, the user will be given information that this is normal behavior and they should wait.
...
Note: it is possible that shipping loggers that enter a zone of low connectivity will become overdue in their wake-up. Therefore a tooltip will be added to explain this on the column itself.
...
The chart tab will display the periods of missing data as well as mark the problematic loggers in the dropdown.
...
The data tab will display the loggers with missing data on the columns and the dropdown.
...
The PDF report will also receive a “Pending Data” banner if a report is requested before the shipment can be fully analyzed. The chart will contain some gaps, and loggers with pending data will be marked with a red icon.
...
Other UI Improvements
Display more location data on hover when selecting locations to create shipments
Description: When creating a shipment, users can hover over a location and see its full detail before selecting it.
...
User impact: UX improvement as the user searches for locations during shipment creation, as they will be able to pick the correct one if a location has the same name.
The map can be collapsed and expanded
Description: When viewing shipments, a user will be able to collapse and expand the map.
...
User impact: UX improvement so users have more space to view the details of a shipment.
Other changes
...
6 logger limit for the chart and data tab removed. Note: Having many loggers with a lot of data might make the interface slower.
...
In user management, both for user creation and your own account, we have added a cleaner more reliable international code selector for the phone number
...
Bug fix:
Keep non-closed shipments with an inspection quality set, but left at “not inspected” status from being removed from the shipment list in the UI. There was an edge case in which a user could set a quality status but not an inspection status for a shipment before closing, and that caused it to be removed from the inspection list. Note that the shipment wasn't deleted; users could still search for it.
...
This release is focused on continued improvements to mitigate missing data cases and other user experience improvements. We are also slowly working on making our branding consistent with our new Brand Style Guide.
An overview of all features and improvements is listed below:
...
Login screen styles updated
A new Brand Style Guide has been published at Controlant, and we will be taking incremental steps to align all our branding according to the changes.
In 2.26.0, our login screens have been updated to reflect the lighter and softer approach to design.
...
...
The system will trigger a temperature analysis as soon as a manual data upload event is detected
Instead of relying on a scheduled process, the temperature analysis for Quality Assessment will be triggered as soon as a manual data upload event on a logger marked as missing data is detected. This change was implemented in order to speed up the release and Quality Assessment of shipments and reduce the time and user confusion while waiting for shipments in “Shipment Analysis Issues” to update.
...
Support for 24-hour wake-up interval
In order to support longer battery life and ensure continuous temperature monitoring on longer shipments, Controlant is introducing support for 24-hour wake-up intervals in the Saga loggers. This new setting will be able to be selected during shipment creation as well as set as a template option.
Note: CO.10 will not be supported and will default to its highest interval of 12 hours should the user accidentally select it.
...
Warning to users if they try to manually request a pdf report while the shipment is shipping
We are adding a warning to users trying to manually request reports on shipping shipments to inform them that the data is incomplete and, therefore, should not be used for releasing products.
...
...
Time-out improvements
Description: We have added improvements to our time-out functionality to ensure a more stable connection to our system. The user should only be logged out after 30 minutes of inactivity.
...
Delivery Automation
Description: With this release, Controlant is adding a feature for the automatic delivery of loggers. This feature ensures consistent delivery timestamps across all loggers in a shipment in case of manual data upload event. The change has no impact on customers that are not configured for the testing phase of this feature.
...
Unit-Level Tracking
Description: In this release, Controlant is laying the groundwork to allow tracking of individual units. This validation requirement simply ensures that this configurable feature can be accessed while we test its efficacy on live data. The change has no impact on customers that are not configured for this testing phase.
...
Other changes
Minor bug fixes.