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.3.5 |
|---|---|
| Release Date | 20/02/2020 |
| Other Application Requirements | Check prior versions |
| Warnings or Notices | None |
VDIST-1163 (Bug) - Delivery Instructions were not appearing on the route planning.
| Version | 2.3.4 |
|---|---|
| Release Date | 15/01/2020 |
| Other Application Requirements | Check prior versions |
| Warnings or Notices | None |
| UID | Summary | Issue Type | Affects Version/s | Component/s | Description | Linked to | Config Required | Licensed Module |
|---|---|---|---|---|---|---|---|---|
| VDIST-1127 | Unplanned Delivery - BI | Report | 2.3.1 | BI | New report added which is showing unplanned deliveries defined by manifest date > 7 days No manifest associated | RFC-562 | No | No |
| VDIST- |
| 1140 | Delivery - Status 'P' after booked date entered | Issue | 2. |
| 3. |
| 3 | Deliveries |
The row colour is white and so is the text, therefore the user is unable to see anything.
| After a booking date is entered for a delivery, in the back end the held reason for ‘Awaiting Booking’ is not removed which later causes an issue with the delivery update job from VW, which prevents the delivery from being updated from status P to O. | VW-4630;VSUP-12010;VW-4632;VDIST-1123 | No | No |
| VDIST- |
| 1137 |
| Delivery - View route | Issue | 2. |
| 3. |
| 3 | Route planning - automated | The user has to close and reopen the delivery screen after saving a PD delivery for the charges > 'View Route' button to appear. | No | No | |
| VDIST- |
| 1136 |
| Route planning - multiple manifests per driver | Issue | 2. |
| 3. |
| 3 | Route planning - automated | When multiple manifests are prepared for a driver, the user clicks 'Accept Plan' and all deliveries are put on to a single manifest. | No | No | |
| VDIST- |
| 1135 |
| Route planning - layout | Issue | 2. |
| 3. |
| 3 | Route planning - automated | When a user saves their layout after changing the column sizes, it's not being recalled correctly. | No | No | |
| VDIST- |
| 1129 | User groups - default administrator group | Issue | 2. |
| 3. |
| 3 | General |
Ran various scenarios however this comes down to users data entry so there are other possibilities which are untested.
Vision LIVE v5.0.0 is required for this to work.
The system will refresh the data as the first step when the user clicks View Plan.
- Move ''Manifest Report by' groupbox to next line and place the radio buttons horizontally.
- Add a new group box "Delivery window adjustment for 'same time'" in above vacant location.
- Add two +/- numeric controls labelled 'From mins adj' and 'To mins adj' defaulted to -20 and 10.
- Validation should ensure that the difference between these two are >= 30.
| During the system updates, we need a way to be sure which group is an administrator account, to setup access to new features, new enquiries etc so that customers know they exist. When systems are first setup, an administrator group is created by default. Some customers change the name of this and later may not use it as an administrator group. Changes will be implemented to ensure that there is always a top level administrator group which our accounts will be linked to, as well as the default customer administrator accounts and this will not be able to be changed. | VW-4345;VB-985;VINVOICING-593;VC-2089 | No | No |
| VDIST- |
| 1124 | Depot Plan - Performance | Issue | 2. |
| 3. |
| 3 | Route planning - manual |
PD deliveries are PD, currently it is showing as D.
e.g. Delivery 042254 should be showing kind 'PD' but it's just showing 'D'.
This is from VDIST-837.
| When working with large datasets the new Depot Plan screen can run 100-200% slower than it did before when performing certain tasks. | VSUP-11381;VDIST-1128 | No | No |
| VDIST- |
| 1122 | VBI - Latest update | Issue | 2. |
| 3. |
| 3 |
The issue has been fixed by getting FromTimeAdjustmentMinsForSameTimeWindow and ToTimeAdjustmentMinsForSameTimeWindow times if the delivery windows times are same.
Modified tblDepotRouting added two columns
FromTimeAdjustmentMinsForSameTimeWindow int (default -20)
ToTimeAdjustmentMinsForSameTimeWindow int (default 10)
Added new logic in Route Planning =>View Plan click, wherein the above value will be used to make the difference of 30minutes before sending to PTV.
New issue (VDIST-953) created to address the rest of the changes.
VSUP-7329
VW-2447
VEDI-411
| BI | Include the latest VBI v1.1.3 fixes and updates. | No | No | |||||
| VDIST-1114 | Delivery address - field consistency | Issue | 2.3.0 | Deliveries | On deliveries in the Delivery Point tab the use of the word "Consignee" is inconsistent with the wording we have used elsewhere in the system. This will be renamed to be "Name / Business" Also for consistency and backward compatibility the other field are to have additional identifiers No & Street (Add1) Building Name (Add2) (Add3) Town Search Results also need to be updated. Generic Description would be “DP Name” This is to differentiate it from the Collection Point or intermediate depot point. | RFC-610 | No | No |
| VDIST-1068 | Depot Plan - Column headers | Issue | 2.2.0 | General | On the Depot Plan, unable to move the columns where you want them. | VSUP-11599;VSUP-10338 | No | No |
| VDIST-926 | Transport Item - Tabbing | Issue | 2.1.1 | Maintenance | The tabbing index on some tabs is inconsistent, plus some other validation and display issues. | VSUP-8845;VSUP-10278;VSUP-10479;VW-3919 | No | No |
| VDIST-1104 | Depot Plan - Planned Arrival Time column | Design Change | 2.3.0 | Route planning - automated | Users would like to see the ‘Planned arrival time’ for the manifest shown. | VDIST-828;VSUP-10946 | No | No |
| VDIST-1139 | Deliveries on hold - manual delivery IDs | Bug | 2.3.3 | General | We have a button in each of the tabs to open the delivery, for manual deliveries the '0' prefix is being omitted. | No | No | |
| VDIST- |
| 1138 |
| Route planning - hours | Bug | 2. |
| 3. |
If the delivery is then saved, the price will be over written.
This is only an issue if an old rate has a revised rate.
If delivery is D or I then no recalculations should be performed.
Otherwise it will calculate and if different the user will have to choose an action
"The charge for this delivery (£xx.xx) is different to what the charge would be calculated as now (£yy.yy), do you want to keep the existing charge or update it?"
| 3 | Route planning - automated | The 'hours' displayed in the Depot Plan for all manifests created from the automated route planning do not agree with the values shown to the user in the map table. | No | No | ||||
| VDIST-1132 | Archive delivery - charge tab error | Bug | 2.3.3 | Deliveries | When viewing deliveries within the archive and you switch to the Charges tab, the following error is shown "Column 'TotalPhysicalPallets' does not belong to table tblDelivery". | VSTASK-2060 | No | No |
| VDIST- |
| 1126 |
| Depot Plan - Moving Deliveries | Bug | 2. |
| 3. |
| 3 | Deliveries |
| When moving multiple deliveries it's not updating the manifest details (e.g. drops, weight), nor can the manifest be expanded to see the deliveries beneath it. | VSUP-11598 | No | No |
| VDIST- |
| 1125 | Depot Plan - Repick Documentation | Bug | 2.3.3.1 |
| Route planning - manual | The repick documentation that is meant to generate when finalising manifests does not generate for systems who use depot printing. | VSUP- |
| 11497 | No | No |
| VDIST- |
| 1121 | Route Plan - Accept Plan | Bug | 2. |
| 3. |
| 3 | Route planning - automated | Syntax error when hitting Accept Plan when the data submitted (such as delivery address line 1) contains apostrophes. | VSUP-11363;VCC-881 | No | No |
| VDIST- |
| 1119 | Delivery - Geolocation Restriction | Bug | 2. |
| 3. |
| 3 | Deliveries |
VSUP-8282
VDIST-917
| ;Route planning - manual | Restrictions entered for a postcode are not automatically attached to deliveries to that postcode, and when manually adding them the routing system is not matching the delivery with a suitable driver. | VSUP-11247;VLIVE-202 | No | No |
| VDIST- |
| 1118 | Delivery |
| - |
| Time 2 fields | Bug | 2. |
| 3. |
| 3 | Deliveries |
| When opening a delivery if the TIme2 fields do not have times defined the screen will show the time the delivery was opened. | VSUP-11185 | No | No |
| VDIST- |
| 1098 | Delivery area - category validation | Bug | 2.2.0.1 |
| Maintenance | The category field is not being validated in the delivery area screen. | No | No |
| Version | 2.3.3 |
|---|---|
| Release Date | 19/09/2019 |
| Other Application Requirements | Check prior versions |
| Warnings or Notices | None |
| UID | Summary | Issue Type | Affects Version/s | Component/s | Description | Linked to | Config Required | Licensed Module |
|---|---|---|---|---|---|---|---|---|
| VDIST-1117 | Delivery - time windows | Bug | 2.3.2 | Deliveries | Delivery time windows are not showing when opening deliveries (archived deliveries are fine however). | VSUP-11127 | No | No |
| VDIST- |
| 1111 | VW> VD Update - Missing address details | Bug | 2. |
| 2.0 |
| .2 | Deliveries | Orders were being pulled from VW into VD without their address details being pulled over despite the address being in VW. | VSUP-10975 | No | No |
| VDIST-1092 | Delivery - Confirmation By Carrier | Change | 2. |
| 3. |
| 0 |
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
| Deliveries | Receiving an error when using the F11 key searching for the Carrier in the “Confirmation by Carrier†screen. | No | No |
| Version | 2.3.2 |
|---|---|
| Release Date | 30/08/2019 |
| Other Application Requirements | Check prior versions |
| Warnings or Notices | None |
| UID | Summary | Issue Type | Affects Version/s | Component/s | Description |
|---|
| Linked to | Config Required | Licensed Module |
|---|---|---|
VDIST- |
1112 | Unprinted Manifests Report - Reasons | Bug | 2. |
3.1 |
- 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.
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
General | Due to changes made to the Unprinted Manifests report the reasons are not showing correctly as they did before, it’s showing the same reasons for all deliveries within the manifest, preventing users from easily finding problem deliveries which are holding up the automated manifest prints. | VSUP-11011 | No | No | ||||
VDIST-1109 | Deliveries - Total Weight | Issue | 2.3.1 | Deliveries, Route planning - automated | The total weight for the deliveries is showing incorrectly. | No | No | |
VDIST-1106 | Dashboards - Awaiting POD for Redeliveries | Issue | 2.3.0 | TV / Dashboards | The dashboards are not displaying statistics for the 'Deliveries without POD' when deliveries are redelivered. | No | No |
| Version | 2.3.1 |
|---|---|
| Release Date | 28/08/2019 |
| Other Application Requirements | Check prior versions |
| Warnings or Notices | None |
| UID | Summary | Issue Type | Affects Version/s | Component/s | Description | Linked to | Config Required | Licensed Module | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| VDIST-1105 | Delivery - Incorrect Weights | Bug | 2.3.0 | Deliveries | When creating a delivery, the weight is showing incorrect | No | No | |||||||
| VDIST-8371102 | Route planning with PR and PD delivery kindsImprovementPlan - Drop Order | Bug | 2.13.0We 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 | .Route planning - automated, Route planning - manual | Order of the Drop points are changing from the Route Planner to the Depot Plan | No | No | |||||||
| VDIST-1071 | Report - Orders Report | Bug | 2.3.0 | General | When selecting multiple statuses, the Total for (status) it showing the total for the whole document. | No | No | |||||||
| VDIST-817 | Route planning - Performance issues | Bug1004 | Enquiry 101 Site Manifest Deliveries | Design Change | 2.01.4When creating a routing plan and pressing accept plan, it can take up to 3 minutes before creating the manifests. 5 | BI | Enquiry 101 Site Manifest Deliveries - was created for a specific customer with specific site codes, will now be changed to work for all. | VDIST-1003, VDIST-803 | 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 | 1106 | Dashboards - Awaiting POD for Redeliveries | Issue | 2.3.0 | TV / Dashboards | The dashboards are not displaying statistics for the 'Deliveries without POD' when deliveries are redelivered. | 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 |
...
| 1007 | VW > VD customer import - email | Issue | 2.2.0 | General | The VW to VD customer import job is not defaulting the customer's email address, it'll be changed to do this but users will be permitted to later change the VD email address to something different to the VW record if required. | No | No |
| Version | 2.3.0 |
|---|---|
| Release Date | 20/08/2019 |
| Other Application Requirements | VDG v2.4.3+ |
| Warnings or Notices | None |
| 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: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 ordersComponent/s | Description | Linked to | Config Required | Licensed Module | |||||||
| VDIST-1083 | Manifest & delivery notes - RePick Manifest with driver info | New Feature | 2.2.0 | Deliveries | Stage 1 - when the manifest is finalised, it currently prints the manifest and delivery notes to the printer for the transport teams. It will now also send an email to the DELIVERY DEPOT manifest repick address, this email will contain * Copy of the manifest * A re-pick note which will be designed to print grouped customer and in a summary format allowing multiple on a page where possible. | RFC-562 | 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-6230772 | Delivery quotation - haulier job acceptance email | New Feature | 1.13.3 | Report Template | Automatic email sent to haulier address when confirming the job with the selected haulier. | RFC-211 | 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-61931009 | Planning Screen Enhancements | Improvement | 2.1.5 | Route planning - manual | Depot Plan 1) Ability to open a delivery from the window 2) Add Delivery Date filter and default it to be UPTO and Including the date selected. 3) Change Picked in Advance to Advanced Deliveries, showing deliveries where the calculated date is beyond the next delivery date 4) Finalisation of the manifest shoudl print manual as well as VW notes, also including replanned deliveries as the first note should not be considered as being available. Route Plan 1) Delivery Date should be UPTO and including the date selected 2) Bottom right hand grid for consignments to choose needs to be made larger both in height and width if possible Delivery 1) Change Weight to be Line Weight to stop needing to calculate the weight manually. | No | No | |
| VDIST-885 | Delivery Note: Delivery Note lines showing differently to Delivery | Bug940 | Integrate VBI 1.1.1 | Improvement | 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-5838General | Integration of the latest version of VBI to fix some bugs & minor improvements. | No | No | |||||||||||
| VDIST-883 | Delivery Charge: Total Delivery Charge is slightly lower than Delivery Area Charge | Bug918 | Reason / problem codes for ePOD | Improvement | 2.1.0 | Delivery Area Charge is doing different rounding (or rounding at a different time) than the Total Deliver Charge. | VSUP-5728 | 1 | Maintenance | A new field to control if problem / reason codes are available to ePOD, to be used in a future version of ePOD. | No | No | |||||||||
| VDIST-879 | Home order deliveries not updating to status O when added to a bulk pick | Bug882 | Manifest search screen - postcode | Improvement | 2.1.0 | Home order deliveries added to a bulk pick are not getting updated from status P to O. | VSUP-51591 | Nav - Form | The postcode will be shown to the left of the drop number on the screen which loads from the manifest search result, this will help looking into issues with ePODs and missing signatures. | VDIST-676 | 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 only857 | Manifest Finalisation | Improvement | 2.1.0 | Route planning - manual | Add a new service against the carrier / carrier item called "Send finalised manifest via email" A new email field will be needed and if the carrier is set to send it will send for all vehicles (items) alternatively if only set for the item then just sends for the item. When the job is finalised the service will poll the manifests and decide if it needs to send the information (manifest) as a pdf to the email address, should the carrier have the haulier extract marked as needed this will also be sent on the same email at the same time. One email to one manifest. The system will also have to show if a manifest has been emailed, and at what time. | No | No | ||
| VDIST-874 | Transport Item Screen - Error when double clicking search results | Issue829 | Route planning - consignments columns | Improvement | 2.1.0When 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 | Route planning - automated | The 'Order Date' will be added to the list of available columns for the consignments grids. | 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-4687828 | Depot plan enhancements for manifests created by route planning | Improvement | 2.1.0 | Route planning - automated | Users would like to see the following fields for the manifest shown: - Total KM - Total duty hours - Planned arrival time ...these cannot be recalculated so any manual adjustments to the results by users (for example adding new deliveries to the manifest) would result in erroneous records, as such any manually edited by the users would need to be marked as such and displayed in the front end and saved. | No | No | ||
| VDIST-8551050 | Pallet charging - lines with 1 CPP | Issue | Delivery - Charges for D / I status | Design Change | 2.2.0.4Delivery 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 | Deliveries | When deliveries are being updated to status D/I many fields in the charge tab appear to be wiped, this is because the values are calculated, but we don't recalculate for D/I status deliveries, as such the fields will be saved and displayed instead. | VSUP-9688 | No | No | |||||||||||
| VDIST-8531080 | Apostrophe in Transport Item address field causes error. | BugTransport dashboards - return deliveries | Issue | 2.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 | General | The transport dashboards are including return deliveries in the outstanding deliveries / manifests stats. | No | No | |||||||||||
| VDIST-850 | VW to VDIST deliveries import job slowing system | Bug1075 | Delivery - Charge band | Issue | 2.12.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.1 | Deliveries | Users are unable to change the charge band, the system keeps reverting it. A 'Fixed' checkbox has been added to allow the user to fix the charge band. | VDIST-1062, VSUP-9688 | No | No | |||||||||
| VDIST-849 | Epod delivery note: duplicate lines | Bug1070 | Manifest Search - Cancelled order | Issue | 2.3.0.4When generating a POD from distribution, the emailed POD will contain duplicate order lines under certain circumstances | Deliveries | When an order is cancelled in VW but if the manifest was already created, upon searching for the manifest number it shows an error. | No | No | ||||||||||||
| VDIST-848 | Unscheduled Deliveries > Not showing details | Bug1057 | Depot Plan - Finalising multiple | Issue | 2.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 | General | If we manually choose more than one manifest to finalise, only first manifest was getting printed. | VDIST-927 | No | No | |||||||||
| VDIST-8471051 | 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 despatchedCreate Delivery - Specify Times | Issue | 2.2.0 | Deliveries | Error occurred upon saving the delivery once the 'Specify time' is checked and then unchecked and then delivery saved. | No | No | |||||||||||
| VDIST-846 | Pick up Return - Epod options not updated | Bug1017 | Depot plan - changing a delivery's depot | Issue | 2.1.0When 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 Warehousing5 | Deliveries | When moving Delivery's to another Depot it is slower in comparison to the Depot Plan (Old) screen. It also keeps changing to the 'Past' tab. | VSUP-9160 | No | No | |||||||||||
| VDIST-8411003 | Depot selection - Incorrect depot selected. | BugDeliveries held - auto released too early | Issue | 2.1.0When 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 rates5 | General | Deliveries are being taken off hold whilst awaiting user restriction confirmation when they are picked. They should remain on hold until the confirmation is received. | No | No | |||||||||||||
| VDIST-840 | Invoice Cases field is not recalculated correctly on deliveries with multiple lines | Bug | 1.12.4, 999 | Manifest Message for ePOD - scrolling | Issue | 2.1.05 | General | 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 | using the scrollbar to go to the bottom of the screen, the last manifest is getting cut off. | No | No | |||||||||
| VDIST-837 | Route planning with PR and PD delivery kinds | Improvement992 | Delivery lines - proportionate value | Issue | 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 Plan4 | Deliveries | Against the delivery lines we store the invoice cases to get an idea of the proportionate value of each line when compared to the overall delivery charge. A problem occurs when we have a delivery with one line, for 11 singles of a 12 pack which charges an overall 1 total invoice case but at the line we have 0.917. A change will be made to introduce a new field to store the correct proportionate value of the line when compared to the delivery total, which would show 1 or 100% in the example above. | No | No | |||||||||||||
| VDIST-831 | System performance | Bug946 | Depot Plan - Speed up | Issue | 2.0.4In the background, the delivery status is being updated too often an causing performance issues1.0 | Route planning - manual | The "new" depot plan is still slower to use when compared to the "Old Depot Plan", this will be fixed so we can later remove the "Old Depot Plan". | No | No | ||||||||||||
| VDIST-830 | Route Planning: Issue when planning on a Friday | Bug-927 | Depot plan - finalising multiple | Issue | 2.01.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 | 1 | Deliveries | Users can only finalise one manifest or ALL manifests - an error appears if the user selects multiple manifests and clicks on 'Finalise Selected'. | No | No | |||||||||
| VDIST-8261088 | Route planning - Edit coordinates restriction | ImprovementDepot plan - moving deliveries | Bug | 2.1.0We would like to restrict the access to the 'Edit coordinates' button used across all screens to certain user groups.6 | Route planning - manual | Depot plan screen has various issues when moving a delivery from one manifest to another. | VSUP-10544 | No | No | ||||||||||||
| VDIST-825Delivery Kind PD > Depot Plan1064 | Enquiry - Unprinted Manifest Report | Bug | 2.12.0 | Delivery Kind - PD is not showing up in the Depot Plan | VSUP-3580General | After changes made on VDG-107 the Unprinted manifest report is not clearing manifests that have generated. | VSUP-10142, VDG-110 | No | No | ||||||||||||
| VDIST-8231052Manifest - Delivery can be added to multiple manifests at the same time | Pre-Advice - EDI Pick Up and Returns charge issues | 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 timeDeliveries | Pick up + Return Deliveries created through EDI are not pulling through their charges correctly and therefore are not applying Transport discounts, however, VW Pre-Advice does show correctly. | VSUP-35389617 | No | No | |||||||||||||
| VDIST-821Deliveries on Hold screen - not checking whether Delivery has been picked.1047 | Route Planning - Accept Plan speed | Bug | 2.0.4, 2.1.0When 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 VW6 | Route planning - automated | After clicking Accept plan the system takes too long to save each manifest. | VSUP-34159671 | No | No | |||||||||||||
| VDIST-8201040Route | planned manifests - report timeDelivery - Site code | Bug | 2.01.4Any manifests created by the route planning engine are not having the 'Driver Report Time' set correctly.6 | Deliveries | There are instances whereby the delivery site code is being reset to the first site (when the same customer code is setup against multiple site codes). | VSUP-9591 | No | No | |||||||||||||
| VDIST-8171039Route planning | - Performance issuesLoad plan - PD kind | Bug | 2.2.0.4When creating a routing plan and pressing accept plan, it can take up to 3 minutes before creating the manifests. | Deliveries | Load plan - Pickup & Delivery kind deliveries are not available in the create load plan screen. | No | No | ||||||||||||||
| VDIST-816Costs Module Issues1035 | Route Planning - PR delivery travel time | Bug | 2.1.0Costs 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 5 | Route planning - automated | When using the automated route planning screen for a pickup (and return stock to depot), the map appears to be showing the route correctly however the results table is not, some issues fixed in VDIST-1012 except for the travel time, this issue will complete the last of the PR issues. | No | No |
| Version | 2.2.0 |
|---|---|
| Release Date | 10/05/2019 |
| Other Application Requirements | Vision Live v5.2.3+ (for route planning) |
| Warnings or Notices | VDIST-647: The default columns displayed in the Depot Plan are changing, if you find that one of the columns you use has disappeared then right click the column headings, select 'Field Chooser' and add it back in to the desired position. VDIST-1048: The routing engine providers have a bug in their service requiring you to set the drivers 'max transport point count per tour' to an additional +1 to work correctly. The fix is available and our server update is being arranged. The field can be set correctly after the server is updated. |
| UID | Summary | Issue Type | Affects Version/s | Component/s | Description | Linked to | Config Required | Licensed Module | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| VDIST-695 | Report - Manifest | Report | 2.1.1 | Report Template | Improve the Manifest to bring it in line with the functionality available in the system with concise terms I *Despatch Information* 1. Site column - Renamed to Dispatching Address - Displays the full address of the dispatching location. 2. Despatch Date - The dates when the goods are due to be picked up from the dispatching warehouse. 3. Despatch Time - The time when the goods are due to be picked up from the dispatching warehouse. II *Delivery Point Information* 1. Name column - Renamed to Destination Address. Displays the name, addressline1, town, postcode of the destination location. 2. Booked Date - This is the date when the goods are due to be delivered to Destination Address. 3. Booked Time - This is the time when the goods are due to be delivered to desintation address. It should print in DROP Order as per route planning, if automated planning is done then estimated times should be shown. If there are different types of deliveries, such as pick up and drop elsewhere each is to have its own section as they would not be within the depot Delivery or pick and return. | RFC-121 | No | No | ||||||||||||||||
| VDIST-1048 | Route plan - Multiple deliveries to same address | Issue | 2.1.6 | Route planning - automated | When multiple deliveries are being delivered to the same address they are not considered at the same delivery for the transport item 'Max Transport Point Count Per Tour' setting. A new depot setting will be added 'Accumulate delivery stops by address' to enable this. | VLIVE-169, VSUP-9299 | No | No | ||||||||||||||||
| VDIST-1046 | Delivery - Manifest Message Screen | Issue | 2.2.0 | General | Receiving an error when clicking Search in the Manifest Message screen. | No | No | |||||||||||||||||
| VDIST-7951031 | Route planning - coordinate retrieval stops | BugCreate Delivery - Save | Issue | 2.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 | Deliveries | While trying to create delivery and click Save button, it is not validating the postcode address automatically. | No | No | ||||||||||||||
| VDIST-792 | Change to the transport extract | Report1023 | Transport Item - Exception | Issue | 2.01.0 | Need the Transport Extract to only have orders on it with deliveries that have been manifested and finalised. | RFC-226 | 6 | Maintenance | While trying to edit Delivery Depots tab under View/Edit Transport Item screen, it shows an exception. | No | No | ||||||||||||
| VDIST-784Held Reasons not being deleted from tblDeliveryHeld805 | Route Planning - Top Filters | Issue | 2.0.0Deliveries are remaining 'on hold' even if the delivery address has been validated and the delivery has gone to 'O'1.0 | Route planning - automated | The filters on the screen are being applied to the selected items, when they should only apply to the unselected deliveries on the left side. | VDIST-787 | No | No | ||||||||||||||||
| VDIST-783 | Address coordinate accuracy | Bug1008 | TV screen stats | Improvement | 2.01.0Improvements to the accuracy of coordinates retrieved5 | General | The stats TV screen has had some improvements following feedback. | No | No | |||||||||||||||
| VDIST-782 | Route Planner Delivery Locks | Issue676 | Nav - View Manifest | Improvement | 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. 1.5 | Nav - Form | View manifest The grid will be updated to the new version and will be tidied up at the same time, new changes will be introduced to make it easier to see potential issues on current routes, including: * Highlighting of delivery times when revised ETAs do not fall between the delivery windows * Highlighting of the revised ETA if more than 2 hours outside of the originally calculated ETA * Delivered lines will be greyed out but still visible * Ordering the grid by drop number A new BI enquiry will also be created showing similar information but problem lines only. Manifest search Will be improved to allow finding a manifest by customer information (i.e. customer code, doc ref, postcode) to facilitate finding a manifest out for delivery and seeing the above screen giving a good idea of the current status for any chasing customers. | RFC-43 | No | No | ||||||
| VDIST-766 | Delivery And Archive Delivery screens - hide route planning buttons for certain delivery statuses | Issue647 | Distribution Planning - Depot Plan | Improvement | 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. | 1.4 | Route planning - manual | Improvements to the Depot Planning Screen Have the ability to show the following fields on the screen to assist with planning: - Delivery area ...plus the new EDI fields from Delivery Option, below: - Service Codes - indication that there are codes and display on mouseover - Service Level - display this field - Area Number - display this field Changes to the default columns displayed will be made but the existing 'Field chooser' available by right clicking the column headings will have all fields available for users to choose which fields they prefer to see. | RFC-8 | No | No |
| VDIST-727 | Vehicle type screen issues | Issue1036 | Depot Plan - Moving a delivery back | Bug | 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.6 | Deliveries | When moving all the Deliveries to a Manifest you are unable to move one back to the left hand side. | No | No | |||
| VDIST-1021 | Geolocation Restriction - adding service code | Bug | 2.1.5 | Maintenance | When trying to add a service code to a Geolocation Restriction on systems with large datasets the process is timing out which is resulting in a BMC error being thrown. | VSUP-9222 | No | No |
| VDIST-1016 | Delivery - Charge pop up | Bug | 2.1.5 | Deliveries | If you change the Charge on a Delivery and click the Recalculate Charges button the message window that pops up is confusing and the first time you make a choice, clicking the Recalculate button will show the message again but not afterwards. | VSUP-9161 | No | No |
| VDIST-1012 | Route Planning - PR deliveries | Bug | 2.1.5 | Route planning - automated | When using the automated route planning screen for a pickup (and return stock to depot), the map appears to be showing the route correctly however the results table is not. | No | No |