SCM release notes v2.25.x

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.

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.

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

Along 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.

Before

After

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.

We have increased the character limit for Inspection Comment to 2000 to give our users more flexibility when inspecting shipments.

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.

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.