SCM v2.27.0 Release Announcement
- Sanna (Susanne) Arthur (Deactivated)
- Víkingur Goði Sigurðarson
- Tara Peters
The 2.27.0 release will be available on the UAT environment from Dec 19, 2023. The planned live release date is Jan 23, 2024.
With the 2.27.0 release, we are adding various exciting new features and improvements to our SCM platform.
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.
For more details on all new features and improvements, keep reading.
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.
Requirements
New
SCMRS-636 | A Reason for Change will be required when a Ready shipment is Deleted |
SCMRS-635 | A Reason for Change is not required when deleting Draft Shipments |
SCMRS-624 | Reason for change cannot be empty or contain only white spaces if the configuration is turned on, and a change is submitted |
SCMRS-623 | When a Reason for Change is entered it should appear in the Audit Trail |
SCMRS-622 | User is able to enter up to 250 characters as a Reason for Change |
SCMRS-621 | A Reason for Change will be required when a location is edited |
SCMRS-620 | A Reason for Change will be required when a template is edited |
SCMRS-616 | A Reason for Change will be required when a shipment is Canceled |
Updated Dec 19, 2023: Requirement “SCMRS-617 Reason for Change setting is configurable per client” was removed from the list because it was being tested by the other requirements.
User impact
If the customer turns on the configuration for the specific action in Account Admin, all users who try to perform the action will be prompted to enter a comment that the Audit Trail will capture. |
There will be an additional operation overhead as those actions will take a little more time to execute while the user enters the comments. |
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.
Requirements
New
SCMRS-628 | A shipment can have a tracking number associated with it |
User impact
None until the configuration is turned on. The current implementation does not have any automations associated with it. It simply links a tracking number to a shipment and displays it in the UI and can only be done through 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.
Requirements
New
SCMRS-625 | A Loggerless Shipment is supported by the system |
SCMRS-627 | A User cannot see temperature information on a Loggerless Shipment |
SCMRS-630 | A user can manually Ship and Deliver a Loggerless Shipment |
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. If this is something you may be interested in, please contact your Customer Success representative.
Requirements
New
SCMRS-615 | A user with an email address subscribed to a shipment notification lane will receive an email with the shipment information |
User impact
None. This is a backend capability and not yet exposed to a UI in its trial phase. |
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.
Requirements
Changed
SCMRS-253 | User is able to update inspection status for an delivered shipment |
User impact
Changes to the date picker flow on shipment and logger send/receive modals. |
Additional review step for manual inspection modal. |
Style updates on all modals in our interface. |
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.
Requirements
New
SCMRS-642 | Pending data banner is visible in pdf report when a shipment in a closed state has data gaps and is configured so |
SCMRS-643 | Pending data icons are visible in pdf report when a shipment has data gaps |
Changed
SCMRS-605 | Pending data banner is visible in pdf report when a shipment in a delivered state has data gaps |
User impact
No user impact unless configured not to show pending data banner. |
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.
Requirements
New
SCMRS-614 | User can see the logger location history on a map of the logger chart tab |
User impact
User will be able to see past locations of a logger that is not in a shipment. |
Delivery Automation
Updated Dec 13, 2023
Requirement added to support Delivery Automation based on location.
Requirements
New
SCMRS-637 | It is possible to set a Delivery Automation rule based on location lanes |
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 (updated Dec 13, 2023)
Other changes
Minor bug fixes
For any questions or concerns, please contact support@controlant.com.
Kind regards,
Controlant Product Team