The main change in the SCM v2.23.0 release is the SCM UI framework port from Angular JS to React.
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.
SCM UI framework port
Description: Due to end of life support for the UI framework Angular JS we are porting the UI to 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 in separate sections below.
This has been a very large undertaking by front end 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 note that we do expect that 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 required functionality would be 1:1 to previous system.
It is noted that Controlant is running a full validation for this release.
Impact:
The change should have minimal impact for the user beside an updated style, look and feel. Changes where the functionality is impacted additionally are listed separately below.
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 reorganized 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 users chooses to skip a template a warning is displayed. This is to reduce the risk of users not creating shipment based on properties.
Create shipment: Logger selection
Logger that has been selected for a logger slot is now removed from the logger dropdown list for subsequent logger slots.
Properties
A back button is added to the edit properties view. This is to make 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 bee 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
Discontinues 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 old shipments, as long as they are not longer than 150 days. Previously the shipment analysis tool did not consider shipments if they were created more than 150 days in the past.
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
Kind regards,
Ragnar Gylfason
Product Manager, SCM