Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Page Properties

Release date

Release type

Minor

Table of Contents
minLevel1
maxLevel2
outlinefalse
typelist
printablefalse


SCM v2.27.0 is the 2023 quarter 4 release. The planned release date is and the functionality will be available on the UAT testing environment from .

This release focuses on compliance, with Reason for change prompts being added to various parts of the interface to ensure traceability when a user edits GxP data.

In addition, we are setting up the platform for future capabilities by allowing a carrier tracking number to be added to a shipment and by creating a new type of shipment that can be managed without loggers. With these improvements, we hope to soon expand automation possibilities in our system through carrier events and get another step closer to a full zero-touch release.

Other improvements include a modification to the pending data banner in shipment reports and the possibility of viewing the logger location history for loggers that are not in an active shipment.

Finally, we continue on our journey of design consistency by updating all our UI modals and improving the UX in our interface.


Reason for change

A configuration was added in SCM that will force a user to enter a Reason for change whenever GxP data is edited. The configurations will be implemented in phases. In this build, we are adding it to:

  • Shipment cancel and delete (excluding drafts)

  • Template edit and delete

  • Locations edit and delete

The configuration is located in Account Admin under settings:

Once turned on, a text field will appear, forcing the user to enter the comment when the key actions are triggered.

 

Once submitted, the action will be attached to the audit entry in our new Audit Trails.


Add your tracking number

As the first step in enhancing our shipments with carrier events, we will now allow our customers to add a tracking number to their shipments in a new dedicated field.

The attached ID will be visible in the UI in the Shipment view:

 

We will continue building out this capability to increase our support for visibility and automation, moving us ever closer to a zero-touch release process. Please get in touch with your Customer Success representative if you're interested in this development and would like to ask questions or provide feedback.

Note: Adding a tracking number is currently only supported through our Customer Integrations API.


Shipments without loggers

To expand the platform capabilities, we are adding an option for customers to create shipments without loggers. This option will only be available through Customer Integrations API and cannot be created manually in our interface.

Shipments created without loggers will have a label in the UI for differentiation.

 

Currently, customers will only be able to ship and deliver these shipments manually or through integrations until automations are added to the system in a future update.


Shipment notification (beta)

A shipment status notification trial with one of our customers has been set up to allow email addresses to be subscribed to Shipment sent notifications based on lanes. In the email, users not only will receive the shipment information, but also a list of loggers and their details. If this is something you may be interested in, please contact your Customer Success representative.


Modal updates

Modals in SCM have been updated to follow our new design style guide and to improve some UX flows.

One such change was to remove the “Now” option when shipping or delivering shipments and loggers to streamline the user flow. The user will by default be set to the current time, but they can change the dates manually right away.

 

An extra preview step was added to the manual inspection modal to allow users to review their changes before saving.

 


Configurable pending data banner in shipment report

A configuration option is being added to the system, allowing customers to either show or hide the pending data banner in the shipment report if the quality status has been manually set.

The default configuration is to show the banner, so there is no impact unless the configuration is set to hide the banner. The configuration is on the account level.


Logger trace functionality

This functionality will improve logger management by allowing users to see the past locations of a logger from the Logger tab without having to assign the logger to a shipment.


Delivery Automation

Requirement added to support Delivery Automation based on location.


Easy copy

A copy button will be available in key areas and shown on hover to make it easier for the user to copy data from SCM UI.


Audit Trail UI bug fixes

  • Change to timezone display in Audit Records. Previously, the system timezone was used for displaying time. After the change, the displayed time will depend on the timezone chosen under display settings.

  • Changed the color of the ID/Reference field in the Audit Trail UI.

  • Added Clear filters button to clear filters after conducting a search for audit records.

  • Added functionality so when clicking on an ID or reference in the right side navigation it triggers a search for that specific ID or reference.

  • Added the ability to select all of the loggers in the chart drop menu with one checkbox


Other changes

  • Minor bug fixes