Here you will be able to view the documentation showing all changes that have been made to Vision Distribution and ePOD The documents list details of bug fixes, improvements and new features that have been implemented in order to enhance the way that Vision Distribution works. Where a new feature has been added, you will be able to link directly to the user manual page giving details of how the new feature works and what it does. You will also be able to view the details of changes which are due to take place in future releases of Vision Distribution. |
|---|
| Version | 2.1.4 |
|---|---|
| Release Date | 15/08/18 |
| Other Application Requirements | |
| Warnings or Notices | Operational changes are marked in RED on the lines below. Please pay attention to these changes. |
Only 2 bugs were fixed which were in v 2.1.2
Vision Distribution v2.1.2 (09/08/2018)
Some users may find it necessary to 'Reset Layout' in the Depot Plan after upgrading
| Issue key | Summary | Issue Type | Affects Version/s | Description | Links | Configuration Needed | Licensed Module |
|---|---|---|---|---|---|---|---|
| VDIST-917 | On time | Issue | 2.1.1 | The 'on time' calculation used to determine if a delivery is on time (used in the OTIF report & stats TV board) is too strict and will be changed as follows: - For fixed delivery bookings (where the from time and to time are the same), deliveries will be considered 'on time' if they are confirmed before the time or up to 10 minutes after. - Other deliveries will also be considered on time if they are confirmed 10 minutes either side of the delivery window. - If the delivery has a reason code with responsibility 'Customer no fault' (was 'other') or 'Transporter no fault' (new) then these will also be considered on time. | No | No | |
| VDIST-855 | Pallet charging - lines with 1 CPP | Issue | 2.0.4 | Delivery lines with 1 CPP are calculating 5 cases as 5 pallets for charging resulting in incorrect delivery charges. If the CPP is 0 or 1 then we'll use the system default for the calculation. It must be completely transparent to users how the invoice cases / invoice pallets / and total charge are calculated. | VSUP-6050 | No | No |
| VDIST-837 | Route planning with PR and PD delivery kinds | Improvement | 2.1.0 | We need to handle delivery kinds "Pickup & Return to Depot" and "Pickup & Delivery elsewhere" differently with the new route planning feature to make the planned routes more efficient. After this change, PRs and PDs will be treated as two part deliveries with the route engine automatically putting the pickup part ahead of the delivery part. Any pickups going back to the depot will treat the depot as an additional delivery point to the manifest and it'll plan the depot drop off for the most efficient point of the route. | No | No | |
| VDIST-817 | Route planning - Performance issues | Bug | 2.0.4 | When creating a routing plan and pressing accept plan, it can take up to 3 minutes before creating the manifests. | No | No | |
| VDIST-814 | New Depot Plan: Gaps left in manifest grid after deliveries removed. | Bug | 2.0.4, 2.1.0 | Gaps are left at the top of the list of deliveries left on a manifest after some deliveries removed. | VSUP-3365 | No | No |
| VDIST-813 | New Depot Plan: Drag and drop delivery to different Depot not working. | Bug | 2.0.4 | Dragging and dropping a Delivery onto a different depot is not working on New Depot Plan screen. | VSUP-3365 | No | No |
| VDIST-784 | Held Reasons not being deleted from tblDeliveryHeld | Issue | 2.0.0 | Deliveries are remaining 'on hold' even if the delivery address has been validated and the delivery has gone to 'O' | No | No |
Vision Distribution v2.1.1 (31/05/2018)
| UID | Summary | Issue Type | Affects Version/s | Description | Links | Configuration Needed | Licensed Module |
|---|---|---|---|---|---|---|---|
| VDIST-923 | Re delivery : Invalid Latest Time | Bug | 2.1.0 | When creating a redelivery, the system is not copying the 'Latest Time 2' across to the redelivery record. | EPOD-240, VSUP-6822 | No | No |
| VDIST-917 | On time | Issue | 2.1.1 | The 'on time' calculation used to determine if a delivery is on time (used in the OTIF report & stats TV board) is too strict and will be changed as follows: - For fixed delivery bookings (where the from time and to time are the same), deliveries will be considered 'on time' if they are confirmed before the time or up to 10 minutes after. - Other deliveries will also be considered on time if they are confirmed 10 minutes either side of the delivery window. - If the delivery has a reason code with responsibility 'Customer no fault' (was 'other') or 'Transporter no fault' (new) then these will also be considered on time. | No | No | |
| VDIST-908 | Delivery with booked date using Pallets | Issue | 2.1.1 | When creating a delivery it is not using the Pallets Lead time for manual or VW orders | No | No | |
| VDIST-891 | Delivery: Deliveries can go on hold in VD with no Held reason | Bug | 2.1.0 | Deliveries are going on Hold in VD with no associated held reason. | VSUP-6230 | No | No |
| VDIST-889 | Postcode Lookup: Object reference error if only one BLD value | Bug | 2.1.0 | If a postcode returns address details that only have 1x Sub Building details then the application is throwing an Object Reference error. | VW-3815, VSUP-6167 | No | No |
| VDIST-888 | Signature: Digital ePODs are not being sent out | Bug | 2.1.0 | Digital ePODs are not generating to go out from VD | VSUP-6193 | No | No |
| VDIST-885 | Delivery Note: Delivery Note lines showing differently to Delivery | Bug | 2.1.0 | Some delivery notes are showing with extra lines as well as quantities that are not matching with the delivery in VD or the order in VW. | VSUP-6109, VSUP-6020, VSUP-5838 | No | No |
| VDIST-883 | Delivery Charge: Total Delivery Charge is slightly lower than Delivery Area Charge | Bug | 2.1.0 | Delivery Area Charge is doing different rounding (or rounding at a different time) than the Total Deliver Charge. | VSUP-5728 | No | No |
| VDIST-879 | Home order deliveries not updating to status O when added to a bulk pick | Bug | 2.1.0 | Home order deliveries added to a bulk pick are not getting updated from status P to O. | VSUP-5159 | No | No |
| VDIST-878 | Depot Plan: F11 in Transport Item can open multiple tabs | Bug | 2.1.0 | When using F11 lookup in Depot Plan > (Right Hand Side) > Transport Item it keeps adding an additional search tab each time F11 is used. | VSUP-4919 | No | No |
| VDIST-877 | Manual delivery - Vintage field read only | Bug | 2.1.0 | Creating a Delivery manually, the vintage field is showing as Read only | No | No | |
| VDIST-874 | Transport Item Screen - Error when double clicking search results | Issue | 2.1.0 | When opening up the Transport Item result from the navigation search we're getting an 'Object reference not set to an instance of an object' error. This happens when the customer hasn't configured any vehicle types in the system, and the application needs this for the drop down menu. | No | No | |
| VDIST-873 | VD - Invoice To Customer field on Deliveries changing | Bug | 2.0.4, 2.1.0 | When re-saving a re-delivery where the Invoice Customer does not match the Customer Ref on the delivery the Invoice Customer is reset to the Customer Ref, which can cause issues when the Customer Ref has a Transport Master account | VSUP-6054, VSUP-4653 | No | No |
| VDIST-872 | Route Planning: Archived vehicles show in Transport Items screen | Bug | 2.0.4, 2.1.0 | When using Route Planning if a Transport Item is archived it is still showing in the Transport Items sections so can be added for Routing | VSUP-4687 | No | No |
| VDIST-855 | Pallet charging - lines with 1 CPP | Issue | 2.0.4 | Delivery lines with 1 CPP are calculating 5 cases as 5 pallets for charging resulting in incorrect delivery charges. If the CPP is 0 or 1 then we'll use the system default for the calculation. It must be completely transparent to users how the invoice cases / invoice pallets / and total charge are calculated. | VSUP-6050 | No | No |
| VDIST-853 | Apostrophe in Transport Item address field causes error. | Bug | 2.0.4, 2.1.0 | Trying to add an apostrophe or if one already exists in the address field of the Transport Item (on Vew/Edit Transport Item screen) causes an error that prevents editing that Transport Item. | VSUP-4109 | No | No |
| VDIST-850 | VW to VDIST deliveries import job slowing system | Bug | 2.1.0 | When the deliveries import job runs (importing deliveries from VW into VDIST) it's locking the system for too long causing delays to VDIST users. | VSUP-3968 | No | No |
| VDIST-849 | Epod delivery note: duplicate lines | Bug | 2.0.4 | When generating a POD from distribution, the emailed POD will contain duplicate order lines under certain circumstances. | No | No | |
| VDIST-848 | Unscheduled Deliveries > Not showing details | Bug | 2.0.4 | Customer planned a tour for 61 deliveries however only 60/61 were planned, the final delivery was not planned and was not shown on the 'Unscheduled Deliveries' tab. | VSUP-3646 | No | No |
| VDIST-847 | Manifests - did not print manifest and delivery note | Bug | 2.0.4, 2.1.0 | Manifests and delivery notes will not print if the manifest has been saved but not finalised and then manually despatched | No | No | |
| VDIST-846 | Pick up Return - Epod options not updated | Bug | 2.1.0 | When a pick up return has been sent through EDI > Warehousing > Distribution, on the delivery that has been created the email options will not be ticked if required by the customer as per customer maintenance in Warehousing | No | No | |
| VDIST-841 | Depot selection - Incorrect depot selected. | Bug | 2.1.0 | When a customer is set up to use pallet charges only and a depot specifically for the delivery area exists in distribution for pallet charging, it is not selecting the pallet depot as default. when the customer is using special rates | No | No | |
| VDIST-840 | Invoice Cases field is not recalculated correctly on deliveries with multiple lines | Bug | 1.12.4, 2.1.0 | When there is more than one line on a delivery, the iCases field is not recalculated correctly when the number of Cases on a line is updated. Updating Disc/Surc % field suffers a similar issue. | VSUP-3684 | No | No |
| VDIST-837 | Route planning with PR and PD delivery kinds | Improvement | 2.1.0 | We need to handle delivery kinds "Pickup & Return to Depot" and "Pickup & Delivery elsewhere" differently with the new route planning feature to make the planned routes more efficient. After this change, PRs and PDs will be treated as two part deliveries with the route engine automatically putting the pickup part ahead of the delivery part. Any pickups going back to the depot will treat the depot as an additional delivery point to the manifest and it'll plan the depot drop off for the most efficient point of the route. | No | No | |
| VDIST-834 | Delivery Address: BMC error when Address lines have invalid characters | Bug | 2.0.4, 2.1.0 | If an order is keyed and comes over to VD with any invalid characters in any of the Address line fields a BMC error will be thrown when trying to open the delivery. | VSUP-5628, VSUP-4903, VSUP-3613 | No | No |
| VDIST-833 | Route Planning - Using simple multi-select | Issue | 2.0.4, 2.1.0 | When clicking consignments or transport items it automatically selects the row and remembers it, it should be using a standard windows selection process like the new Depot Plan. | No | No | |
| VDIST-831 | System performance | Bug | 2.0.4 | In the background, the delivery status is being updated too often an causing performance issues. | No | No | |
| VDIST-830 | Route Planning: Issue when planning on a Friday | Bug | 2.0.4, 2.1.0 | When using the Route Plan to plan for the next week on a Friday, the plan creation process is not being completed correctly instead it is only manifesting the final tour created, the other manifests are created blank with no deliveries on them. | VSUP-3488 | No | No |
| VDIST-826 | Route planning - Edit coordinates restriction | Improvement | 2.1.0 | We would like to restrict the access to the 'Edit coordinates' button used across all screens to certain user groups. | No | No | |
| VDIST-825 | Delivery Kind PD > Depot Plan | Bug | 2.1.0 | Delivery Kind - PD is not showing up in the Depot Plan | VSUP-3580 | No | No |
| VDIST-823 | Manifest - Delivery can be added to multiple manifests at the same time | Bug | 2.0.4, 2.1.0 | If a delivery is added to a manifest and the same delivery is then confirmed with a carrier it will allow for the delivery to be present on 2 manifests at the same time. | VSUP-3538 | No | No |
| VDIST-821 | Deliveries on Hold screen - not checking whether Delivery has been picked. | Bug | 2.0.4, 2.1.0 | When all issues have been resolved on a Delivery in the Deliveries on Hold screen (for example 'Delivery area / depot / charge settings could not be derived from the post code entered' the Delivery should update to Status O when it has already been picked in VW. | VSUP-3415 | No | No |
| VDIST-820 | Route planned manifests - report time | Bug | 2.0.4 | Any manifests created by the route planning engine are not having the 'Driver Report Time' set correctly. | No | ||
| VDIST-817 | Route planning - Performance issues | Bug | 2.0.4 | When creating a routing plan and pressing accept plan, it can take up to 3 minutes before creating the manifests. | No | No | |
| VDIST-816 | Costs Module Issues | Bug | 2.1.0 | Costs added to the delivery (on the Depot Plan screen) are not being save to the database and they should be. Costs added to the manifest do save correctly. | No | No | |
| VDIST-815 | New Depot Plan: Slower than Old Depot Plan | Bug | 2.0.4, 2.1.0 | New Depot Plan is slower when Saving, Adding deliveries to manifests Removing Deliveries from manifests and periodic freezes during use. | VSUP-3365 | No | No |
| VDIST-814 | New Depot Plan: Gaps left in manifest grid after deliveries removed. | Bug | 2.0.4, 2.1.0 | Gaps are left at the top of the list of deliveries left on a manifest after some deliveries removed. | VSUP-3365 | No | No |
| VDIST-813 | New Depot Plan: Drag and drop delivery to different Depot not working. | Bug | 2.0.4 | Dragging and dropping a Delivery onto a different depot is not working on New Depot Plan screen. | VSUP-3365 | No | No |
| VDIST-811 | Delivery status history | Bug | 2.0.4 | A history of delivery statuses is maintained in the back end of the system and this is filling up with duplicates. | No | No | |
| VDIST-810 | Transport Item screen - Error when clicking Save button | Bug | 2.0.4 | Clicking Save button on Transport Item screen shows an error if system is not configured for routing in Vision Live. | VSUP-3405 | No | No |
| VDIST-809 | Transport Item Screen - Error when clicking Save button | Bug | 2.0.4 | Clicking Save button on Transport Item screen throws an error if there are no Driver Regulations records. | VSUP-3405 | No | No |
| VDIST-806 | Apostrophe in Delivery Address causes an error when opening the Delivery. | Bug | 2.0.4, 2.1.0 | An apostrophe entered in to the Delivery Address in VW causes an error when opening the Delivery in Vision Distribution. | VSUP-3360 | No | No |
| VDIST-796 | Route planning - Coordinate retrieval for invalid addresses | Issue | 2.0.4 | When we have an invalid address, the system is currently repeatedly attempting to retrieve the coordinates and failing every time. This will be changed so that after it's been attempted once, it won't continue to try as it's the users responsibility to correct this from the held screen. | No | No | |
| VDIST-795 | Route planning - coordinate retrieval stops | Bug | 2.0.3 | When an address such as "4, Langford Court" exists in the deliveries, when the service attempts to retrieve the coordinates it errors and stops working. | VSUP-6053, VSUP-6029 | No | No |
| VDIST-792 | Change to the transport extract | Report | 2.0.0 | Need the Transport Extract to only have orders on it with deliveries that have been manifested and finalised. | RFC-226 | No | No |
| VDIST-784 | Held Reasons not being deleted from tblDeliveryHeld | Issue | 2.0.0 | Deliveries are remaining 'on hold' even if the delivery address has been validated and the delivery has gone to 'O' | No | No | |
| VDIST-783 | Address coordinate accuracy | Bug | 2.0.0 | Improvements to the accuracy of coordinates retrieved. | No | No | |
| VDIST-782 | Route Planner Delivery Locks | Issue | 2.0.0 | The locks from the Route Planner screen are being deleted when the screen is shut. However, when a(nother) user opens the Route Planner, those deliveries that were left from the 'shutdown' user session are displayed without any locks ! | No | No | |
| VDIST-773 | Route Planing - Deliveries Type | Issue | 2.0.0 | The Consignments section on the Route Planner shows the Deliveries as Non Conformance (Red), when you are searching all of the Types in the search criteria. | No | No | |
| VDIST-766 | Delivery And Archive Delivery screens - hide route planning buttons for certain delivery statuses | Issue | 2.0.0 | Once a delivery has been sent out for delivery, there is no need to have access to the buttons associated with route planning | No | No | |
| VDIST-764 | Map size | Issue | When opening the map from any screen, it currently opens as maximised by default. We sometimes have a grey area at the bottom which we want to avoid, so instead when opening the map from any screen, open the screen at a specific size, still allow the user to maximise if they wish. | No | No | ||
| VDIST-728 | Site & depot screen issues | Issue | Various minor issues. | No | No | ||
| VDIST-727 | Vehicle type screen issues | Issue | 2.1.1 | Various issues with the validation of fields in the vehicle type maintenance screen. | No | No |
Vision Distribution v2.1.0 (20/09/2017)
This release is primarily for integration with VW version 5.0 it will not work with prior versions of Warehousing
In addition the following bugs were resolved
| VDIST-808 | Postcode lookup was not seeing some addresses when they belongs to a single company |
| VDIST-800 | Palletforce FTP - Extract Issues |
| VDIST-799 | Costs Module With the costs module set to on, and the Transport and Transport Item set to "each load will be individually priced" the costs box on the depot planning screen does not allow input of the cost information for the manifest. |
| VDIST-798 | Costs Setup When setting up a transport or transport item and setting the Costs flag to All loads are individually priced the system produces an error "Unable to case object of type "System.Arguement.Exception" |
| VDIST-794 | Carrier Plan → Error when opening. |