| Version | 4.1.0 |
|---|---|
| Release date | 26/04/2019 |
| Other Application Requirements | VD v2.1.0+ / VD v2.2.0 required for configuration of the driver start / end day questions in EPOD-244 |
| Warnings or Notices | Nothing further to add |
| UID | Summary | Issue Type | Affects Version/s | Component/s | Description | Linked to | Configuration Changes | License Required |
|---|---|---|---|---|---|---|---|---|
| EPOD-281 | En route - Google maps integration | New Feature | 4.0.0 | App | Google maps integrated into the new "En Route - Drop information" screen, click on this button to start navigation with google map using the drop's delivery address. | No | No | |
| EPOD-278 | Settings - Defaults | Issue | 4.0.0 | App | The default settings when installing the application / clearing application data should be empty server addresses and carrier information. Currently they're defaulted to the Ontech test system which has been causing issues with devices automatically updating before the customer environment is ready. | VSUP-9648 | No | No |
| EPOD-270 | Main menu - spelling | Issue | 4.0.0 | App | 'VECHILE' should be 'VEHICLE' in the main menu item group headers. | No | No | |
| EPOD-269 | Delivery Line Issue - Column alignment | Issue | 4.0.0 | App | On the Delivery Line Issue screen, the columns are not aligned with the headers. | No | No | |
| EPOD-262 | ETAs - Storage for Vision Distribution | Issue | 4.0.0 | Processor | EPOD will be changed to populate some new VDIST delivery ETA fields when processing the upload message so that all deliveries have an ETA window saved for them. This is required for the API calls from Vision Distribution. | VC-1619 | No | No |
| EPOD-261 | Notification email - Delivery point, customer email address validation | Issue | 4.0.0 | Processor | The email notification to the delivery point is attempting to send when the customer has no email address defined for them, this is unnecessary. | No | No | |
| EPOD-282 | General - Compatibility with Android 9 | Improvement | 4.0.0 | App | Vision ePOD is now compatible with Android Pie (v9). | No | No | |
| EPOD-264 | Device location | Improvement | 4.0.1 | App | Device location will be polled and regularly uploaded direct to Vision Distribution for future analysis and reporting. | No | No | |
| EPOD-233 | Confirm Despatch - Delay | Improvement | 3.2.0 | General | Many drivers leave the depot early to avoid traffic and to perhaps have a break or PNB prior to the start of the deliveries. Add a new option which allows the driver to specify a delay to his departure time. So the options would be Confirm Despatch - leaving depot immedaitely Confirm Despatch - leaving depot in X minutes. If the Confirm despatch is not within 60 minutes of the report time then the user is asked to confirm they are confirming despatch. | No | No | |
| EPOD-271 | Flow of ePOD Improvements | Design Change | 4.0.0 | General | The flow of screens and processes has been streamlined. | No | No | |
| EPOD-263 | DP Notification - From | Bug | 4.0.0 | Processor | The Despatch confirmation email that is sent to the Delivery Point is sending the Depot Postcode in the from segment of the email when it should be sending the Customer name. | VSUP-8591 | No | No |
| EPOD-257 | Delivery Confirmation Email - Line missing | Bug | 3.2.1 | General | When the Confirmation of Delivery email is sent for a delivery which has a item that has been partially delivered it is not showing that line within the email. Where it should be showing the line together with the part delivery quantity. | VSUP-8245 | No | No |
| Version | 4.0.0 |
|---|---|
| Release date | 05/11/2018 |
| Other Application Requirements | VD v2.1.0+ Compatible with this version / VD v2.2.0 required for configuration of the driver start / end day questions in EPOD-244 |
| Warnings or Notices | See above, nothing further to add |
| Issue key | Summary | Issue Type | Affects Version/s | Component/s | Description | Linked to | Configuration Changes | License Required |
|---|---|---|---|---|---|---|---|---|
| EPOD-242 | Rewrite of the existing application | Improvement | 3.3.0 | App | Complete rewrite of the existing application to bring it up to date with the latest user interface standards. | No | No | |
| EPOD-244 | ePOD Driver Start / End of Day questions | New Feature | 3.3.0 | Various | In VDIST v2.2.0+ users can define a set of questions to ask the drivers at the start, end, or start and end of their day. For example, the current vehicle mileage, tyre pressures checked, fuel level, lights working, etc. With this version of ePOD the questions will then be displayed as configured in VDIST and capture the answers from the driver. Date, time, device ID and who are all recorded and stored. | Yes | No | |
| EPOD-253 | Deliveries : 'Confirm PIN' screen PIN number | Improvement | 3.3.0 | App | Upon clicking 'Conf OK', the screen asks for a security pin number and it should display the soft keyboard with numeric values only. | No | No | |
| EPOD-255 | Delivery: Signature not updated on Delivery from EPOD | Bug | 3.2.1 | General | Signature is not uploading from EPOD to VDIST when the name contains an ampersand (&). | VSUP-7322 | No | No |
| EPOD-256 | ETAs - Calculation point / storage | Issue | 3.3.0 | Processor | The ETA is currently calculated when drivers confirm despatch and the message is processed by the server. Later, if an email / SMS is to be sent with a time window, we then calculate the window from this time and send it. The EDI API expects the window from / to fields to be set for all deliveries from the start, the result is that if a delivery doesn't have an email / sms generated for it then the window from / to are empty. EPOD will be changed to populate the window from / to when processing the MT1, so all deliveries have an ETA window saved for them. | VC-860 | No | No |
| EPOD-254 | Delivery ETA SMS not being sent | Bug | 3.3.0 | Processor | Customer doesn't get the morning ETA message, but they are receiving the message and email sent the evening before. | VSUP-7702 | No | No |
| EPOD-226 | Message process delay caused by notifications which cannot be sent | Bug | 3.2.0 | Processor | Notification emails & SMS messages are stored and then processed, in some instances there's no email nor mobile number to send the notification to and these messages build up. Every time the process checks for emails to send, the number accumulates and the process takes longer and longer and this has a knock on affect to the uploaded message processing. | No | No |