...
The change should have minimal impact for the user beside an updated style, look and feel. Changes where the functionality is impacted additionaly are listed seperately below.
Min/Max shown in shipment view
This is the first (mini) step of bringing more data to the shipment view.
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.
...
New requirements:
SCMRS-555: User can see the minimum and maximum recorded temperature values across all loggers in the shipment detail view.
...
Excursion handling
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.
...
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.
...
...
The Excursion Boundaries table will now only show excursions that happened within the monitoring time resulting in the table being displayed as below.
...
User feedback if shipment is recreated with recalled/disabled loggers.
We are currently duplicating a lot of shipments and we are discovering ways we can improve that process and hopefully reduce the need to duplicate in the first place.
There was an urgent need to act quickly, as loggers that are not Active (disabled or recalled) are removed from the duplicated shipment. There are checks to ensure shipments are not created with inactive loggers and duplicating a shipment is indeed creating a new shipment.
However, it is not the simplest task for the user to detect this removal of loggers from the shipment and this has led to cases where a shipment arrives and a report is generated but missing a logger without an explanation.
To mitigate this we added two steps.
First, there is an error message in the pop-up modal.
...
Second, after the logger has been removed there will be an empty logger slot, indicating that there should have been a logger which is no longer there and preventing the user to immediately Ready the duplicated shipment without tending to the empty logger slot.
...
Warning when manually requesting report with missing data.
It was identified as a risk for a couple of customers that users might request a shipment report through the SCM UI wihtout realising the the shipment is missing data.
The shipment report does not yet reflect this status. To minimize risk and clarifying the status the following message was added to the request report modal.
...
Preview of new style
Main view
The main changes in the main view is the style of the “Create shpment button” and the Shipments, Loggers and Locations tabs are now more like buttons instead of tabs.
 |  |
Single shipment view
Only styling changes were made and everything was left in the same place as before.
 |  |
...
Other changes
...
Please get in touch with me with any questions or concerns at ragnar@controlant.com
...