The main change in the
| Table of Contents | ||||
|---|---|---|---|---|
|
...
In this SCM v2.23.0 release is a UI the biggest focus was on performing a framework port on the SCM user interface from Angular JS to React. There are some changes in the system as a result of that.This will result in better maintainability, improved speed of the user interface and enhanced scalability. This will benefit both our development teams and our customers.
In addition to the framework port, we have added some improvements to styling, how information is presented and small non-breaking changes to the user flow.
Overview of all features and improvements can be found here listed below:
...
SCM UI framework port
Description: Due to end of life support for the UI framework Angular JS we are porting the UI to the React framework. The plan was to do the move from Angular JS to React where the functionality would remain 1:1, resulting in minimal impact for the user.
We did however, see some opportunities for minor functionality improvements and these are listed separately belowin separate sections below.
This has been a very large undertaking by the front end development team and as such we have been very diligent with our testing efforts to support this change. Nonetheless, we can never be 100% sure that everything is caught during testing so we want to note that we do expect some maintenance patches will be required following the live deployment of this change.
Requirement impact:
No requirements are changing because of the release as the change was made so that the functionality would be , as we kept a 1:1 to migration from the previous system.
Please note that Controlant is running a full validation for this release.
...
The change should have minimal impact for the user beside an updated style, look and feel. Changes where the functionality is impacted additionaly additionally are listed seperately separately 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.
...
Main view
The main changes in the main view is the style of the “Create shipment 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.
 |  |
...
UI changes as a result of the framework port
This chapter lists the minor UI changes that were made.
Create shipment flow
Create shipment: Strengthening create shipments as templates as the default flow.
The first step of manual create shipment process was re-organized to encourage users to select a template instead of a custom shipment.
The default process is to select a template and the alternative option is Skip template.
...
If the user chooses to skip a template a warning is displayed. This is to reduce the risk of users not creating shipment based on templates.
...
Create shipment: Logger selection
Logger that has been selected for a logger slot is now removed from the logger dropdown list to reduce the cognitive load of previously selected loggers.
...
Properties
A back button is added to the edit properties view. This is to make the navigation easier.
...
...
Updates in the product module
This chapter lists the changes that were made specifically within the Products section of the UI.
Products: Banner added to indicate product impact in single product view.
This is to further clarify for the user if there is a possible product impact or not.
...
Alternatively, if product stability budget is exceeded the message becomes a yellow warning as indicated below.
...
Products: In case there are multiple conditions, breached conditions are greyed out.
When one stability budget criteria for products with multiple criteria is breached, that criteria will be shown as greyed out. This is to indicate that the product quality is not compromised but this criteria should no longer be considered.
...
Products: Logger dropdown in single product view cleaned up.
The logger dropdown selection has been cleaned up. The icon indicating the result has been moved in front of the logger ID and the sensor ID has been removed (:DE:0)
...
Products: Back button added in single product view.
Back button added to single product view. This button returns the user to the Products list.
...
Other changes
Discontinued support of old firmware version of CO 10.01. These are only about 500 devices globally that will be disabled, most on internal accounts and none have reported to the cloud for more than a year.
Allowing processing of shipments that were started more than 150 days ago. This is a slight change and impacts only a few edge cases shipments. Previously the shipment analysis tool did not consider shipments if they were created more than 150 days in the past. But now if the duration of the shipment is within the 150 day limit - the system does not care when the shipment was started.
Requirement SCMRS-300: User is able to create project location has been deactivated as it is a duplicate of requirement SCMRS-330: Admin user is able to associate a global location to a project. This change does not impact the functionality or the solution in any way, it is simply a requirement clean up procedure.
...
Please get in touch with me with any questions or concerns at ragnar@controlant.com
...