...
Here you will be able to view the documentation showing all changes that have been made to Vision Distribution and ePOD
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. |
|---|
...
Vision Distribution v2.1.1 (31/05/2018)
...
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
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.
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"
| Version | 2.12.60 |
|---|---|
| Release Date | 1510/0305/192019 |
| Other Application Requirements | Vision Live v5.0.0For Route planning2.3+ (for route planning) |
| Warnings or Notices | Operational changes are marked in RED on the lines below. Please pay attention to these changes. |
To reproduce
Select Today + 1 tab
Click Add manifest, a new manifest is created in the grid.
Click save without updating Transport Item.
We should get '..Invalid driver code..' error text in the column, however it is not showing when we go to Today +1 tab.
This is causing issues stopping the automated routing from working.
Vision Live v5.0.0+ for Route planning
VDG v2.4.2+ (not compulsory but includes depot printing fixes)
Operational changes are marked in RED on the lines below.
Please pay attention to these changes.
The row colour is white and so is the text, therefore the user is unable to see anything.
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.
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.
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
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?"
VSUP-8282
VDIST-917
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
...
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-1031 | Create Delivery - Save | Issue | 2.2.0 | Deliveries | While trying to create delivery and click Save button, it is not validating the postcode address automatically. | No | No | |
| VDIST-1023 | Transport Item - Exception | Issue | 2.1.6 | Maintenance | While trying to edit Delivery Depots tab under View/Edit Transport Item screen, it shows an exception. | No | No | |
| VDIST-805 | Route Planning - Top Filters | Issue | 2.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-1008 | TV screen stats | Improvement | 2.1.5 | General | The stats TV screen has had some improvements following feedback. | No | No | |
| VDIST-676 | Nav - View Manifest | Improvement | 2.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-647 | Distribution Planning - Depot Plan | Improvement | 2.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-1036 | Depot Plan - Moving a delivery back | Bug | 2.1.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 |