Version 1.5.0 – Release Date 25/04/25
Change Type | Description |
Enhancement |
Enhancements around Proof of Delivery Functionality:
|
Enhancement |
Improvements to the Proof of Delivery List/Card:
|
Improvements to how shipments are Invoiced.
Currently if the full quantity is shipped, but in PODFather, other Proof of Delivery Integrations or by entering a manual Proof of Delivery it is recorded that less was delivered (or there was a failed delivery), due to an delivery issue or rejected or missing items there is no visibility of this and this results in the full quantity being involved.
The following changes have been made:
|
|
Enhancement |
Added Functionality to view Posted Warehouse Documents against a Shipment Management Route Card |
Enhancement |
Added Functionality to allow Users to be able to Split Drops if it is not possible to deliver the whole of a Source Document Line on one Route (i.e. as it is not possible to fit on the delivery vehicle), it is now possible to split a source line. |
Enhancement |
Collect-from Address Functionality has been added to Sales Return Orders. Collect-from address allow the user to specify the address that should be used to collect the goods from. This can either be a Ship-to address or manually entered. Note: This is common functionality that also supports Clever Shipping Agent Integration. |
Enhancement |
Delivery Area code has added to the Customer List and the Ship-To Address List. |
Enhancement |
Added ability to Suppress the Date Check that the shipment date (or cut-off time) was in the past when releasing a source document. The error will still be shown by default. |
Enhancement |
Improvements to Shipment Management Vehicles:
|
Enhancement |
Added New Functions to Shipment Management Entries which allow Users to be able to Remove Entries from a Route. |
Enhancement |
Warning notification added to the Shipment Management Routes List Page if there are Routes filtered out due to the default date filter. This can be disabled or enabled per user from the My Settings Function. |
Enhancement |
Add Contact Details to Drop Address Page. |
Improvements to Reservation Handling:
|
|
Enhancement |
Warning added when changing Shipping Advice if a Route is already in progress. |
Enhancement |
Business Central Compatibility Changes:
|
Bug Fix | Resolved Issue where the Delivery Order was not getting correctly set if using the 'Select Customers...' action on the Delivery Area page |
Bug Fix | Resolved Issue around the reservation checks on Sales Orders were not correctly handling Special Orders. |
Bug Fix | If there is a Sales Order with two lines but these lines are on different Routes to one another. When processing a Route for Line 1 to create picks, post shipments, etc. it also does the same action for Shipment that exists for Line 2. This is now resolved for Warehouse Shipments, Warehouse Picks, Warehouse Put-aways and Warehouse Receipts. |
Bug Fix | When moving Drops using the Move Drops Function, occasionally the old Shipment Management entry record would be left as an orphaned record. |
Azure Maps Integration | |
Enhancement |
Due to the pending deprecation of Bing Maps, Azure Maps equivalents of the following pages have been added:
In addition once the Azure Maps integration has been enabled geo-coding of addresses and route optimisation will now use Azure Maps APIs as opposed to the Bing Maps APIs. Map functionality in currently like for like with the previous Bing Maps functionality except for the enhancements listed below. |
Enhancement |
Ability to show traffic information on planning and route maps (Azure Maps only). |
Enhancement |
Ability to print a route map (Azure Maps only). |
Enhancement |
Ability to overlay a driving range on the planning maps and delivery area map to aid with planning routes/drops (Azure Maps only). |
Enhancement |
Improvements to the pin colours to make drop pins easier to see with a clearer legend (Azure Maps only). |
Enhancement |
Ability to optimise a route from actions within the route map (Azure Maps only). |
Enhancement |
Ability to create and save sets of default filters for the Drops by Location/Date Map (Azure Maps only). |
Enhancement |
Ability to amend filters applied to the Drops by Location/Date Map (Both Bing and Azure Maps) |
Bug Fix |
Some addresses were not correctly geo-coded with certain address formats. |
PODFather Integration | |
Enhancement | Added Support for Vehicle Types |
Enhancement | Added support for Synchronising Vehicles and Vehicles Types. |
Enhancement |
New PODFather Settings Page to allow PODFather Integration Settings to be amended after the Integration has been Enabled. |
Enhancement | Added support for downloading Vehicle Checks and storing these against the Vehicle record. This will also update key information against the vehicle such as the last recorded mileage which can be utilised for servicing requirements. |
Enhancement | Support for Item Variants. The PODFather integration now supports Item Variants and these will be correctly recorded in returned Proofs of Delivery. The way Item Variants are displayed in PODFather can be defined in the PODFather Settings. |
Enhancement | Improved Error Dialog for PODFather Synchronisation issues to make it easier to diagnose problems. |
Enhancement | The Source (i.e. Route Number) has been added to the PODFather API Log with an action to take the user to the corresponding record. |
Enhancement |
Addition of a New Status Type called PODs Completed Status which can be used to check that the Proof of Delivery Documents have all been synched from PODFather back to Business Central before a Route can be completed. |
Enhancement | Support for PODFather Notifications via e-mail or SMS. These can be optionally set against the Customer or Ship-to Address for Delivery Planned, Delivery ETA Updates and Delivery Completed notifications. There is a new Shipping Contact on the Customer Card to support this as notifications may need to be sent to different contact to the standard contact. |
Enhancement | Added ability to set drops as Provisional in PODFather. This prevents them being sent directly to the handheld devices. This can be set in the PODFather Settings. |
Enhancement | Added Functionality to prevent a Drop/Entry from being moved if it has already been synched with PODFather. |
Enhancement | Flexibility over the item quantity that is sent to PODFather. This can now be the Source Document Quantity, Shipped Quantity or Reserved Quantity. |
Enhancement | PODFather Integration now supports custom (manually entered) ship-to address entered on Sales Documents. |
Enhancement | Improved security on PODFather Integration. |
Enhancement | The Delivery Area/Route Description will now be shown on the PODFather Run (Route). |
Bug Fix | Drop Timeslots will now be correctly sent to PODFather |
Bug Fix | Prevent drops that have been sent to PODFather from being rescheduled. |
Bug Fix | The Sales Line Gross Weight was being sent to PODFather instead of the Unit Gross Weight. |
Bug Fix | The developer events against the PODFather integrations have been amended to allow the message bodies to be altered by extensions extending the functionality in Shipment Management. |
Version 1.4.9 – Release Date 07/01/25
Change Type | Description |
Enhancement |
Introduction of new consistent onboarding functionality.
|
Enhancement |
Help links updated to support the Chat with Copilot feature (In supported regions).
|
Enhancement |
Full integration with Clever Shipping Agent Integration. If using both Clever Shipment Management and Clever Shipping Agent Integration, it is now possible to create the packages for the consignment directly from the Shipment Management route. This is a new status to support this.
|
Enhancement |
Integration with Clever Document Delivery. If Clever Document Delivery is installed it is now possible to use Document Delivery to send documents specified in the Print Documentation status.
|
Enhancement |
PODFather Integration Improvements:
|
Enhancement |
User interface improvements to the Posted Shipment Management routes:
Note: The Amount Inc. Vat (LCY) and Amount Exc. Vat (LCY) fields will only be populated for new routes created and not for existing posted routes. |
Bug Fix |
If you delete a Customer or Customer Ship-to address, then the related entry is not removed to any Delivery Areas it was assigned to. |
Bug Fix |
When Enabling reservation checks on sales documents and checking the Shipping Advice, the system would incorrectly check for reservation against Items of type 'Service' or 'Non-Inventory'. |
Bug Fix |
Issue when using the Posted Doc. Lines to Reverse action on a Sales Return Order. |
Bug Fix |
Issue with wrong shipping agent usage and charge calculation being applied when using post code regions. |
Bug Fix |
In a very rare circumstance Shipment Management might try and re-use the same route number if the preceding route was completed without any warehouse documents being posted. |
Version 1.4.8 – Release Date 03/10/24
Change Type | Description |
Enhancement |
New Events in codeunit 9094429 "Get Delivery Area CSPMTMN":
|
Bug Fix |
Resolved Issue with Converting Sales Quotes to Orders for Assemble-to-Order Items |
Bug Fix |
Resolved Issue with Shipment Date Rescheduling if Outside the Scheduling Time Period |
Version 1.4.7 – Release Date 18/09/24
Change Type | Description |
Enhancement |
Added New Functionality to cater for Third-Party Transport. Clever Shipment Management now supports using a third-party transport company to fulfil a shipment management route. The changes include a new transport booking worksheet, additional status types to support the process and improvements to the status list setup wizard to support setting up this process. |
Enhancement |
New option when calculating Shipping Charges to always include the shipping line even if the charge was zero (Free Delivery). |
Enhancement |
Improved support for Directed Put-Away and Pick locations. If using Directed Put-Away and Pick there are now alternative Create Picks status types to either create Warehouse Picks per Zone or Warehouse Zone and Bin combination. |
Enhancement |
Support for Clever Quality. If Clever Quality is installed then two new status types are available to support Inbound Quality Checks and Outbound Quality Checks for Warehouse Receipts Pre-Posting Checks and Warehouse Shipment Pre-Posting Checks. |
Enhancement |
Support for Clever Printer Selections. If Clever Printing Selections are enabled for the relevant documents used by Shipment Management with a printer service provider (i.e. Clever print Node Integration) the documents will be routed to the specified printer for direct printing. |
Enhancement |
If a report is specified in the Print Documentation Status but there are no records to print then the error message will now be supressed. This allows for scenarios that you may specify multiple reports that may only be applicable to certain use cases. |
Enhancement |
Improvements to the Move Drops Functionality to warn Users if they manually select a Route with a Shipment Date which is in the past. |
Enhancement |
To help with route planning the Route cut-off date and time (if specified) will now be shown on the Shipment Management Route Factbox and possible Routes lookup. |
Enhancement |
New events in Codeunit 9094436 "Schedule Rec CSPMTMN":
|
Enhancement |
BC24 and BC25 Compatibility Changes:
|
Bug Fix |
Change to the tooltip on the route display window field on shipment management setup as it was misleading. |
Bug Fix |
When a new route is selected, on the Move Lines function, the Description did not default to the new Delivery Area Code |
Bug Fix |
When using Clever Shipment Management with Clever Comments, if there were multiple delivery comments against the source document then only the first was getting inherited to the drop. |
Bug Fix |
Resolved Issue with Non-Inventory Items being included in Shipment Management Entries. |
Bug Fix |
Resolved Issue around the formatting of the vehicle specification fields causing an error to be displayed on the route map. |
Bug Fix |
When converting a Sales Quote to a Sales Order then the delivery area and therefore route do not get assigned to lines on the new Sales Order. |
Bug Fix |
When releasing a document the check if the route was in the past was not respecting cut-off times. |
Bug Fix |
In some cases the Work Date was being used instead of the current date. If the Work Date was in the past this could result in a route being suggested that was before the current date and therefore not possible to deliver. |
Bug Fix |
If a status was set as both Hidden and to process automatically then a 'Only routes with the same status code list and status code can be processed together' was incorrectly shown with processing the previous status. |
Bug Fix |
If there were multiple documents in the Print Documentation status and Show Options page was not enabled for each report they only the last report would be downloaded, due to web client restrictions. In this scenario all documents will now be downloaded in a Zip file. |
Bug Fix |
Resolved Issues with Filtering on the Shipping Agent Usage and Charges Page |
Version 1.4.6 – Release Date 16/07/24
Change Type | Description |
Bug Fix |
PODFather Integration - Resolved Issue with the Qty Consigned Field not being Updated Correctly on Proof of Delivery Documents. |
Version 1.4.5 – Release Date 11/07/24
Change Type | Description |
Enhancement |
PODFather Enhancement - Delivery Notes entered against Items on the Device are now recorded against the Proof of Delivery Lines in Business Central |
Bug Fix |
Resolved Issue with the Sell-To Address on Sales Returns Orders. Now, if the address is updated, it is correctly reflected against the Shipment Management Route |
Bug Fix |
Resolved Issue with Adding New Drops to a Route after the Picks for the existing Drops on the Route have been created. Now Picks are created for the new Drops correctly. |
Bug Fix |
Resolved Issues around Synching FROM and TO PodFather |
Bug Fix |
Resolved Issue with using Item Substitutions Functionality. Any Items which have been substituted are now added to the Route correctly. |
Bug Fix |
Resolved Issue with the Move Drops Page where it showed Completed Routes. |
Version 1.4.4 – Release Date 17/06/24
Change Type | Description |
Enhancement |
Changes to Resolve Issues with using Clever WMS Devices to process Picks and not being able to completely Pick all the total quantity. We have now amended the functionality to take into account the Device Suspended Field |
Enhancement |
Improved Response Messages from PODFather |
Enhancement |
Improvement to Assisted Setup |
Enhancement |
New Welcome Page when Installing from Appsource to assist first time Users |
Enhancement |
Add Delivery Instruction Flag to Drops Page |
Enhancement |
Changes to Display on Routes for Date/Location Map to cater for multiple Drops to the same Address |
Bug Fix |
Resolved Issue with Drops not being Added to a Route when using the Get Posted Document Lines to Reverse Functionality |
Bug Fix |
Resolved Issue with Wrong Page Opening on Manage Locations Button on Assisted Setup Wizard |
Bug Fix |
Resolve Spelling Mistake Issue on Proof of Delivery Reason Object Name |
Bug Fix |
Resolved Issue with Inherited Shipment Management Drop Comments not Copied to Delivery Instructions |
Bug Fix |
Resolved Issue with Error which occurs when using Recurring Sales/Purchases Line and Automatic Insert Option |
Bug Fix |
Resolved Issue with Drop Markers showing Incorrect Colours on Date/Location Map if there are more than 3 Routes |
Bug Fix |
Resolved Issue with Synching POD's from PODFather to Business Central |
Bug Fix |
Resolved Error which occured when removing the Date Filter on Route Maps |
Version 1.4.3 – Release Date 04/04/24
Change Type | Description |
Enhancement |
Added New Event OnBeforeCheckShipmentDatesOnRelease |
Bug Fix |
Resolved Issue with Nested Error Handlings Causing Errors on Shipment Route Status |
Version 1.4.2 – Release Date 28/03/24
Change Type | Description |
Enhancement |
Added Base Calendars to Ship-To Address Card to allow users to define the days you cannot deliver. |
Enhancement |
A Route Assignment Field has been added to Route Status Lists to allow Users to control if Source Documents should be assigned to a Route at the point each line is entered or when the Source Document is Released. |
Enhancement |
In previous versions, Clever Shipment Management worked differently on Purchase Documents due to the lack of Shipping Agent and Shipping Agent Service Fields. This was limiting for the addition of new functionality added for other types of documents so we added functionality to make assigning Purchase Documents to Shipment Management Routes work consistent with Sales Documents. |
Enhancement |
If Clever Shipment Management detects that Clever Comments is installed, additional Inheritance options will be available on the Comment Type Page allowing comments to be inherited onto Shipment Management Drops. |
Enhancement |
Added functionality to allow Delivery Instructions to be formattable and allow unlimited characters. |
Enhancement |
Addition of a new Assisted Setup Wizard to allow Users to be able to setup all aspects of Clever Shipment Management quickly and easily. |
Enhancement |
Added the Route Description onto the Routes for Date/Location Map |
Enhancement |
Added Functionality to allow Users to be able to move part of Drop onto a new Shipment Management Route. Previously this was limited to just being able to move a whole Drop. |
Enhancement |
BC24 Compatibility Updates:
|
Enhancement |
Addition of New Events:
|
Bug Fix |
Resolved Error which appeared when Installing/Upgrading Clever Shipment Management in French Environments |
Bug Fix |
Resolved Issue with Variant Code not Updating correctly on Shipment Management Routes |
Bug Fix |
Resolved Issue which allowed multiple Shipment Management Routes to be processed together when they were at different Stauses |
Bug Fix |
Resolved Issue which sometimes showed Drops on Bing Maps in the wrong place |
Version 1.4.1 – Release Date 13/02/24
Change Type | Description |
Enhancement |
Added a check to the Sales Order Release Function to see if the Shipment Date on any of the sales lines is in the past. If they are, a message will be displayed allowing the user to reschedule the sales lines to a new Delivery Date/Route. This check has been implemented to provide a smoother integration with Clever Credit. If you look at the example of a document being Credit Held and then not being released for a few days, then the Route it was initially added against could have potentially already been processed and the Credit Controller would not be aware of that. |
Bug Fix |
Remove the Mark Non-Inventory Lines as Shipped Heading from Warehouse Shipment Page |
Bug Fix |
Resolved the error which appeared when selecting the Previous Status option from the Shipment Management Route list. |
Version 1.4 - Release Date 06/02/24
Change Type | Description |
Enhancement |
Various Enhancements to Route Status Lists
NOTE - For users which are upgrading to 1.4 from an earlier version, please also refer to this Page for more information on the Route Status Upgrade process Route Status List Changes (Version 1.4) |
Enhancement |
Addition of new Status Types:
|
Enhancement |
Various Enhancements to the Create Status List Wizard:
|
Enhancement |
Improved support for Reservations within Clever Shipment Management:
|
Enhancement |
Various Enhancements to Route Status Maps:
|
Enhancement |
Route Optimisation (if enabled via Bing Maps Integration) will now take into account truck routing (if vehicle specification entered against vehicle). On completing optimisation users will now be presented with an option to show the changes on the route map. |
Enhancement |
Improvements to the default Shipping Manifest Document:
|
Enhancement |
Service Orders are now supported by Clever Shipment Management. Changes made to support this are:
|
Enhancement |
Ability to change Shipping Agents/Shipping Agent Services on Multiple Routes. New batch job to allow the Shipping Agent (and/or Service) to be reassigned on multiple routes and, optionally, Source documents, warehouse documents and master data. Can be run from the Shipment Management Role Centre, Shipping Agent page or Shipping Agent Service page. |
Enhancement |
Improvements to Vehicles records as per the following:
|
Enhancement |
Improvements to Drivers records to include the following:
|
Enhancement |
A new Description field has been added to Shipment Management Route List, Card and Move Pages to make it easier to identify routes. This will default to the Delivery Area description but may be edited. |
Enhancement |
The Shipment Management Route Factbox has been added to the Warehouse Shipment List and Card and Warehouse Receipt List and Card. |
Enhancement |
Improvements to Handling Failed Deliveries. The drop now has a new entries option to show Rescheduled Entries. when a failed delivery is rescheduled the existing entry will be deleted and a new rescheduled entry will be created so it is easier to view the new route the goods will be shipped on. |
Enhancement |
New setup option to Archive Shipment Management Routes once they have been completed. |
Enhancement |
New Pages have been added to show all Shipment Management Drops in a single list. This allows users to utilise the new Analyse Functionality (part of standard Business Central) and query the data. The new Page names are shown below and they can be found by using the standard Business Central Search Functionality:
|
Enhancement |
Improved Onboarding Experience:
|
Enhancement | New dedicated Role Centre for Shipment Management called Shipment Management Planner |
Enhancement |
The Status Factbox on Routes has been extended to now show more status codes as not all were not all visible when using complicated warehouse processes. |
Enhancement |
|
Enhancement |
For Purchase Orders the collection date is now linked to the Planned Receipt Date instead of the Expected Receipt Date. The Expected Receipt Date is calculated as standard by adding inbound warehouse handling time and the safety lead time to the planned receipt date, therefore if you’re going to collect a purchase order, you need to collect it on the Planned Receipt Date so that it’s available in the warehouse for the Expected Receipt Date. |
Enhancement |
The following APIs have been added to support additional integration scenarios:
|
Enhancement |
The following External Business Events have been added to support additional integration scenarios:
|
Enhancement |
New Events have been added to enable further customisations:
|
Enhancement |
The Resource Exposure Policy has been amended to make it easier for partners to support and extend Clever Shipment Management. |
Enhancement |
Business Central Compatibility Changes :
|
Enhancement |
Change to Report Selections - Shipment Management Page to combine the Shipping Manifest and Proof of Delivery Pages into one. |
Bug Fix |
Resolved Issue with the Move Up/Down Actions to change the delivery order for Shipment Management Drops. This may not work in some scenarios where two or more additional drops are moved to the route. |
Bug Fix |
Resolved the "Sales Line does not exist" error which occurred when using the Copy Document Functions on Sales Orders and not copying the Header. |
Bug Fix |
Resolved the "Sales Line does not exist" error which occurred when moving lines onto a new Shipment Management Route and deleting Sales Order Lines. |
Bug Fix |
Resolved issue with the Departure Time from Delivery Schedules not being respected and set correctly in the Route Start Date/Time Field on Shipment Management Routes. |
Bug Fix |
Resolved error which occurred when renaming an Item which has Variants defined. |
Bug Fix |
Resolved Issue with the Register Pick Status if the Prevent Processing from Route Field is Enabled. If the Pick was processed in the Warehouse before the Status on the Shipment Management Route was set, then it was not possible to move onto the next Status. |
Bug Fix |
Added a message to Shipment Management Routes when the last Drop is removed asking if you wanted to delete it. |
Bug Fix |
Resolved issue around an error occurring when creating Transfer Orders from Requisition Worksheets when they relate to a Shipment Management Route. |
Bug Fix |
Resolved issue with the Shipment Date Field not always being set correctly on the source document line when moving a route. |
Bug Fix |
Resolved issue with the FlowField Filters used on the Drop Time Slot Field on the Shipment Management Drops Page. |
Bug Fix |
Resolved Issue with the Tooltip being incorrect for the Reservation Status Field on the Create Status List Wizard. |
Version 1.3.1 (Release Date 12/04/23)
Change Type | Description |
Enhancement |
Handling Failed Deliveries. This release adds the ability to handle drops that you are then not able to deliver. This is controlled by a new option on the status list that determines at what Status codes failed deliveries can be handled. With this release there are two possibilities to handle failed deliveries:
|
Enhancement |
Support for Clever Containers Shipment Bins. If using Shipment Management in conjunction with Clever Containers, then any Shipment Bin defined for a Location/Shipping Agent/Shipping Agent Service can be defaulted onto the route. |
Enhancement |
Vehicle Locations added. This allows both the restriction of which locations a vehicle can operate from but also to specify Shipment Bins specific to a location\vehicle combination. |
Enhancement |
Maximum Capacity (Volume) added to the vehicle. This will also highlight on the routes/drops page if the combined totals of the items volumes exceed capacity. |
Enhancement |
The Source Document Status and Document Credit Status are now shown on the Shipment Management Entries List. This makes it easier to see document assigned to a route that have not been released. If using in conjunction with Clever Credit, this also gives visibility of the credit status of documents added to a route. |
Enhancement |
In previous releases you could not use the Move Line function if there was a Warehouse Shipment related to an entry on the drop, even if the current status allowed this. In this release this restriction has been reduced so it will only apply if the Shipment Management entry is part of a consolidated Warehouse Shipment. |
Enhancement |
This release makes it easier to view Posted Shipment Management Entries against a route. |
Enhancement |
On the Gross Weight and Volume Totals (and selected drop totals), it is now possible to see the percentage load and maximum allowed value of the vehicle if a vehicle is assigned to the route and the maximum weights and volumes are held against the vehicle. This makes it easier to plan loads. |
Enhancement |
If setting up shipping charges it is now possible to use a Non-Inventory Item for the Shipping Charges instead of a G/L account or Item Charge. |
Enhancement |
Business Central Compatibility Changes:
|
Bug Fix |
The error message displayed during the Move Lines function now correctly shows the actual Drop No. as opposed to the Drop Entry No. |
Bug Fix |
If deleting a Route then any open/credit held documents assigned to the Route but not a drop will have now have the Route No. field cleared on the source document. |
Bug Fix |
A spurious warning message when using Shipment Management in combination with Order promising is no longer shown. |
Bug Fix |
An issue where two event subscribers both tried to update the Delivery Area Code field on a customer when using the Call Log functionality has been resolved. |
Bug Fix |
An issue in the upgrade routine that occurred if there was an existing route without a Shipment Date/Expected Receipt Date has been resolved. |
Bug Fix |
When drilling down into drops, the selected lines totals would only show the last line selected not the totals of lines selected. |
Version 1.3.0 (Released 22/11/22)
Change Type | Description |
Enhancement |
Integration with PODFather Software for Route Planning and Proof of Delivery Functionality More information about PODFather and their products can be found here https://thepodfather.com/ |
Enhancement |
New optional status type 'Load Vehicle' for any load checks and to trigger third-party integrations. |
Enhancement | |
Enhancement | |
Enhancement |
Added Ability to control against a Route Status whether new drops can be added from source documents |
Enhancement | |
Enhancement |
Added Support for Delivery Instructions against a Shipment Management Route |
Enhancement | |
Enhancement |
Enhanced Onboarding Experience which includes:
|
Enhancement | |
Enhancement |
Allow integration with Bing Maps to show enhanced drop address and to optimise drop order |
Enhancement |
Business Central Compatibility Changes:
|
Bug Fix |
Resolved Issue with the 'Complete Assembly' status to allow partial shipments when components are not fully picked. |
Bug Fix |
Resolved issue with lines not being added to a Shipment Management Route correctly on a Sales Return Order when added using the 'Get Posted Document Line to Reverse' Function |
Bug Fix |
Resolved Issue around Changing Purchasing Codes on Sales Lines not updating the Delivery Area correctly |
Bug Fix |
Resolved Issue with Shipment Management Routes not being created correctly when a 'Location' and 'Shipping Agent' were added to the Sales Document |
Bug Fix |
Resolved Issue with Shipment Management Routes not being updated when using 'Order Promising' |
Bug Fix |
Resolved issue with the 'Collection Date' not being copied onto new Purchase Lines |
Bug Fix |
Resolved issue which caused an error to appear when Recurring Sales Lines were inserted automatically |
Bug Fix |
Resolved Issue with the Calculation of VAT Fields on Shipment Management Entries Page |
Known Issue |
The Book Time Slot Functionality cannot be used with PODFather. This will be resolved once an updated version of the PODFather API has been released. |
Version 1.2.1 (Released 10/02/22)
Version 1.2 (Released 25/01/22)
Change Type | Description |
Enhancement | Support for Collections. Clever Shipment Management has new status types to support the handling of warehouse documents related to collections:
|
Enhancement | Support for Transfer Orders |
Enhancement | Support for Sales Orders containing make-to-order production orders and assemble to order assembly orders. |
Enhancement | New wizard to simplify the setup of the status list. |
Enhancement | Status type list. Lists available status types to avoid having to know the processing codeunit. This is fully extensible to support custom status types. |
Enhancement | Improved status error handling. Each status can be set to either stop or proceed if an error occurs using the new ‘Error Policy’ field. |
Enhancement | Route status log. The new log function captures the start date and time of each status and any errors that occurred on that status irrespective of the new Error policy setting. |
Enhancement | Improved visual display of route status. The fact box now shows a visual display that makes the current status much easier to see for the end-user. Colour coding is all used everywhere to status is shown to make it clearer if an error has occurred. |
Enhancement |
Additional Checkpoint status types. The following new checkpoint status types are available:
|
Enhancement |
Improved integration with Clever Handheld for Warehousing and standard warehouse documents. When posting/registering the following warehouse document types in either Clever Handheld for Warehousing or using standard Warehouse documents Clever Shipment Management will move the status on to the next status and respect the option on whether to process automatically if it is the last document related to the route:
|
Enhancement | Clever shipment management will now respect the settings for Shipping Agent Integration and trigger the consignment when processing warehouse shipments. |
Enhancement | The full address of a drop can now be viewed from an action the drop list. |
Enhancement | A Bings maps representation of the route can be displayed from the Route List Card. |
Enhancement | Support for Variant Codes on Shipment Management Entries. |
Enhancement | The default filters on the route list have been improved. The location filter will now include all locations that the user is set-up to manage in the Warehouse Employees rather than just the default location. The default date filter will now show all routes earlier than todays’ date that have yet to be completed and it is possible to set a datefomula in the Shipment Management set-up to define the default forward window to view. |
Enhancement | Duplicate route warning. When moving a drop to a new route a check is now made to see if this would create a duplicate route. |
Enhancement | The total weight will now be highlighted red if the weight exceeds that of the vehicle. The Gross and Unladen Weight of the vehicle can now be recorded and used in weight checks. |
Enhancement | Improved filtering on the Move Lines action on the drop list. The dialog and filter options when selecting a route via the move lines function has been changed to improve usability. |
Enhancement | Improvements to show source document information on entries and drill-down on drops. |
Enhancement | A new factbox on the sales order and sales return order allows instant visibility of the shipment/collection date, route number, status and drop number. |
Enhancement | It is now possible to select a possible route from the sales order from available dates the route can be made as opposed to always being the next available date. This means it is possible to ship nearer or on the customer’s requested delivery date. |
Enhancement | It is now possible to set-up a matrix to default the Shipping Agent and Shipping Agent Service based on weight, volume, value and delivery address of the order. |
Enhancement | It is now possible to add shipping charge lines to a sales order depending on the selected Shipping Agent/Shipping Agent Service. New options on the Warehouse setup allow related shipping charges to be marked as shipped (and invoiced if appropriate) when shipping items from warehouse documents. |
Enhancement | The delivery schedules screen has been simplified for ease of use. Dates now can be viewed in a list or calendar format. |
Enhancement | Excluded dates can now be created on the delivery schedule. This is useful if days of the weeks are normally used in the delivery scheduled but certain dates should be excluded. |
Enhancement | It is now possible to block a vehicle from use whilst retaining information on when the vehicle was previously used. |
Enhancement | It is now possible to see a list of all routes where the vehicle is currently used. This makes it easier to amend those routes if a vehicle is not available for use. |
Enhancement | The history of which routes a vehicle has been used on can now easily be seen from the vehicle record. |
Enhancement | Notes can now be recorded against a vehicle. |
Enhancement | It is now possible to block a driver from use whilst retaining information on when the driver was previously used. |
Enhancement | It is now possible to see a list of all routes where the driver is currently used. This makes it easier to amend those routes if a driver is not available for use. |
Enhancement | The history of which routes a driver has been used on can now easily be seen from the driver record. |
Enhancement | Notes can now be recorded against a driver. |
Bug Fix | Manifest Report is missing default Layout. |
Bug Fix | A Custom (free-entry) shipping address is not respected on a Sales Order. |
Bug Fix | Update Existing Documents Batch Job can miss certain documents. |
Bug Fix | Shipment Management needs to ignore drop shipments. |
Bug Fix | Delete Delivery Schedule to remove Schedule Dates. |
Bug Fix | Printing the Picks using the Print Pick Step does not actually print picks. |
Bug Fix | Issue with App Failing Validation Tests when extending Shipment Management. |
Bug Fix | When adding new lines to the Delivery Area Page, the 'Delivery Order' field should be being populated sequentially i.e. increment by 1 for each new line created. Currently it isn't working like that and it is assigning the 'Delivery Order' values in a different order. |
Bug Fix | Lookup to report ID in report selections only shows ID. |
Bug Fix | Not possible to create ID 1 on Delivery Schedule lines. |
Bug Fix | Strange Drop No. generated if you have multiple Drops on the same Shipment Management Route. |
Bug Fix | Remove Routes with No Drops. |
Version 1.1.23
Change Type | Description |
Enhancement | Update App.Json |
Version 1.1.22
Change Type | Description |
Enhancement | Support Irish Post Codes |
Version 1.1.21
Change Type | Description |
Enhancement | Update ready status on setup change |
Enhancement | Historic routes |
Enhancement | Respect calendar customisation – non-working day to be a working day |
Enhancement | Update tests to run in sandbox container |
Enhancement | Convert custom sorting options to enums and add events into WhseSubscriptions codeunit to allow a custom subscriber to handle a custom value that has been added to the enum and updated the sorting sequence of the pick lines. |
Enhancement | Enforce licensing - Check/create a license when the Shipment Management Routes page is opened. Allow all other logic to run as usual, even in the absence of a license. |
Enhancement | Add Events On Calculating Weights/Volumes on Shipment Mgt. Entries |
Enhancement | Implement Reserve Inventory Status |
Enhancement | BC17 Compatibility |
Enhancement | Delivery schedule dates changed for deliveries outside of regular schedule |
Enhancement | Support Irish & French Postcodes |
Bug Fix | Switching back to Default Shipping Address does not update Del Area on Sales Line |
Version 1.1.14
Change Type | Description |
Enhancement | Respect Customer/Vendor Base Calendar when Scheduling if they have one, base calendar customizations are respected as well as the base calendar itself. |
Version 1.1.12
Change Type | Description |
Enhancement | Update Logo and Manifest for AppSource |
Version 1.1.11
Change Type | Description |
Bug Fix | Fix for postcode overflow error so customer orders that have a postcode of longer than 10 characters can be released to a shipment management route. |
Bug Fix | Fix to mixed drop entries that arise when moving lines from one route to another, if there is already a drop on the route for the same customer and the lines are moved this would create an extra drop on the route as opposed to grouping it onto the same drop no. Fix applied so it finds the existing drop and the shipment management entries under each drop number are for the correct destination number. |
Version 1.1.10
Change Type | Description |
Enhancement | New fields added to shipment management entries list page and available as flow fields to the Drop and Route records: |
Enhancement | Quantity (Base) |
Enhancement |
Amount Exc. VAT (LCY) Amount inc. VAT (LCY) |
Version 1.1.9
Change Type | Description |
Enhancement | Control for Moving Lines/Drops - There is a new column on the Status List page to determine whether drops can be moved to/from a route when it is at this status. |
Enhancement | Print Documentation Including Incorrect Sales Shipments |
Bug Fix | Delivery Order Reset to 0 On Whse. Shipment Posting – this happens when the Posting Date of the Whse. Shipment is different to the Posting Date of the Sales Order(s). In that case, the Sales Order(s) are reopened and released by the standard posting routine which in turn deletes and recreates the Shipment Mgt. Drop records |
Bug Fix | A fix is in place for posting the warehouse shipment from the Shipment Mgt. Route list or card. This behaviour may persist if the warehouse shipment is posted from the Whse. Shipment card page. |
Bug Fix | Reverse delivery order is not sorting by bin code |
Version 1.1.8.2
Change Type | Description |
Enhancement | Create Consolidated Whse. Shipment - Check whether any of the lines on the selected Route will be included on a Warehouse Shipment before creating the shipment header. |
Version 1.1.8.1
Change Type | Description |
Enhancement | Process Non-Next Status Code Requires Shipment Management Supervisor - Extra controls have been introduced when attempting to process a status other than the next planned for a route (either by going to a previous status or selecting a different status in the factbox). Only supervisors – designated on their Warehouse Employee record – can process statuses other than the next. |
Bug Fix | Fix to processing of status codes from Shipment Mgt. Route FactBox |
Bug Fix | Destination No. populated on Shipment Management Entry records |
Bug Fix | Ready flag on Shipment Management Entry records respected in Amount (LCY) flow fields. |
Bug Fix | Handling of lines created/deleted during assembly BOM explosion |
Version 1.1.8
Change Type | Description |
Enhancement | Hide Status - Optionally hide status codes from the factbox with the Hide Status checkbox on the setup page. |
Enhancement | Process Automatically - The “Process Next Immediately” concept has been altered to “Process Automatically”. When ticked this status will be processed immediately the route is updated to it. This allows the user to chain several statuses together e.g. to include codeunits to perform checks on the route before posting documents. |
Enhancement | Linking Report Selections with Route Statuses - A new Status Code field on the Report Selection page allows reports to be linked to a given status code. The SM – Print Documentation codeunit will print records matching the current status code. |
Enhancement | Custom Pick Sorting Includes Bin Code - Sorting by Delivery Order now also sorts by Bin Code within each set of pick lines that share the same delivery order. |
Enhancement | Support for Printing Warehouse Activity Headers in Report Selections - Warehouse Activity Header can now be selected under the “Filter Report By” column on the Report Selection page. The report identified in the “Report ID” column will be filtered to print Warehouse Activity Header records which have at least one line included on the Route that is being printed. |
Enhancement | Highlighting Status Path for Given Shipping Agent - The Route Status List page now includes a Shipping Agent Code field. When this is populated each status that is relevant to the selected agent is highlighted allowing the user to visualise the path through the statuses. |