v3.3.0 01/08/2018)
| UID | Summary | Issue Type | Affects Version/s | Fix Version/s | Description | Linked to | Config Needed | Licensed |
|---|---|---|---|---|---|---|---|---|
| EPOD-239 | SMS Security - TLS deprecation | Improvement | 3.1.6 | 3.2.1 | Upgrade of SMS system to support TLS v1.2 security protocol | No | No | |
| EPOD-232 | End of Day: Ending mileage | Issue | 3.2.1 | 3.3.0 | Users can enter a value into ending mileage that can cause the message to be rejected due to an overflow error. | VSUP-6562 | No | No |
| EPOD-231 | Signature confirmation delays | Issue | 3.2.0 | 3.2.1 | The signature processing continues to be problematic and stops processing during the day. This cannot be replicated anywhere and despite efforts to fix this the issue persists. A recompile of the coding appears to have removed the issue using the latest development tools. | VSUP-6458 | No | No |
| EPOD-226 | Message process delays | Bug | 3.2.0 | 4.0.0 | Message process delay caused by notifications which cannot be sent 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. New flag added to ignore these. | No | No | |
| EPOD-225 | ePOD: Removal of deliveries from manifest | Bug | 3.2.0 | 3.2.1 | When deliveries are removed from a manifest before the Depot Departure has been confirmed and the driver chooses to update the manifest the deliveries that have been removed from VD were not being cleared off the EPOD manifest | VSUP-6202 | No | No |
| EPOD-224 | ePOD Signature: blank signature | Bug | 3.2.0 | 3.2.1 | When going to enter a signature on a delivery there is no validation to prevent a user from entering a blank signature as part of validation. Validation added | VSUP-6179 | No | No |
| EPOD-222 | Signature confirmation - crashing | Bug | 3.2.0 | 3.2.1 | ePODs have communicated to us that in some instances they are crashing during / after signature capture when a very complex and large signature is added, resizing of the image will take place to ensure signature is captured in full at the lowest possible size. | No | No | |
| EPOD-221 | Message processing failing | Bug | 3.1.6 | 3.2.1 | We've seen that message processing can stop and messages build up. When this happens an error is logged on the server. | VSUP-6142 | No | No |
| EPOD-219 | Confirm depot departure - failed message processing | Bug | 3.2.0 | 3.2.1 | Some MT1 (confirm depot departure) are failing, when reposted they process fine. | VCC-433 | No | No |
| EPOD-217 | Arrived time - automate this | Improvement | 3.3.0 | If the driver has not clicked the 'Arrived' button, we will automatically populate this when the driver clicks any of the 'Conf' buttons for a delivery. | No | No | ||
| EPOD-216 | Confirm depot departure - validation | Improvement | 3.3.0 | In Vision Distribution we store the 'Driver Report Time' against each manifest. This is the time the driver is supposed to arrive at the depot to collect their load. Some drivers have been accidentally confirming departure the night before picking up the load, to avoid this we will check before allowing them to confirm if the current date/time is more than an hour either side of the 'Driver Report Time' and then ask them if they're sure they want to confirm departure. | No | No | ||
| EPOD-215 | Sort order - validation | Improvement | 3.3.0 | Extra validation will be added to the delivery sort order screen to help ensure that drivers are entering the drop numbers correctly (e.g. ensuring the number sequence is not broken, new prompt for customers who merge deliveries which haven't been put on to the same drop number). | No | No | ||
| EPOD-208 | Button press | Issue | 3.2.0 | 3.2.0 | On screens where multiple buttons are next to eachother, if you press one, the others change shape too almost appearing if you have pressed them. | No | No | |
| EPOD-207 | Bulk sign | New Feature | 3.2.0 | Deliveries with the same drop number can now be signed for once instead of getting a signature for each delivery. The driver has the control over if this can be done or not. | No | No | ||
| EPOD-204 | Delivery terms & conditions acceptance | New Feature | 3.2.0 | ePOD can now be configured to store T&Cs which the user must accept prior to signing the delivery. Reequires VD v2.1 or later (requires support configuration) | No | No | ||
| EPOD-201 | Device clear down - audit | Issue | 3.1.4 | 3.2.0 | Support received a report that VDIST deliveries had not been updated with the signature from EPOD, they were still status C. Upon further investigation we found that the records did not exist on the device database nor the EPOD server database. The clear down process was checked and found it couldn't have been a problem on the server as we had not passed the 30 day limit for deleting the records, so the problem must have happened on the device. We concluded that they must have been removed by the user as there was evidence of the user clearing the data set. We will start an audit of deleted messages which we'll maintain for 6 months on the device. If this occurs again we can check the date / time the record was deleted and then cross reference this to the logs to try and work out what caused it. | VSUP-4084 | No | No |
| EPOD-190 | General interface | Improvement | 3.2.0 | Small Overhaul of the user interface with various improvements. | No | No | ||
| EPOD-188 | Driver messaging improvements | Improvement | 3.2.0 | The messaging feature will be rewritten to make it a more useful and user friendly feature. | No | No | ||
| EPOD-184 | Display the depot on the manifest list | Improvement | 3.2.0 | The depot for the manifest will be displayed in the manifest lists. | No | No | ||
| EPOD-183 | Delivery signature | Improvement | 3.1.5 | 3.2.0 | The current signature screen requires the user to use the device buttons (usually menu press or hold) to bring up the save / undo options on screen and this has confused a number of users. Improvement to make this more user friendly | No | No | |
| EPOD-175 | Core - Fallback server connection | Improvement | 3.1.2 | 3.2.0 | Primary and secondary server connections are stored in the settings, currently these are used inconsistently throughout the application / background service. This will be changed to use a common process, and when the server 1 address is not available, it'll try the server 2 address (if it's different to Server 1). Only afterwards will the connection fail. | No | No | |
| EPOD-172 | Core - Removal of FTP interface | Improvement | 3.1.5 | 3.2.0 | The FTP interface has been removed and replaced with HTTP connections for DB uploads and photo uploads for deliveries. | No | No | |
| EPOD-115 | Auto Uprade - IMPORTANT | Improvement | 3.1.0 | 3.2.0 | We have implemented new system upgrade process as a part of EPOD-41. But as the version upgrade version need to work for existing version we can't remove some of the files/constants from the application in the VB v3.1.0. So will be removing those in the next release and those changes are noted in the Changes to be made. IT IS IMPORTANT THAT ALL USERS ARE MOVED TO V3.2 as soon as possible otherwise they will not upgrade for v4 | No | No |
v3.1.6 (16/11/2017) - includes updates for various prior releases.
| Issue | Issue Type | Summary | Fix Version/s | Affects Version/s |
|---|---|---|---|---|
| EPOD-187 | Bug | Message processing: Manifest issues downloading to device | 3.1.6 | 3.1.5 |
| EPOD-185 | Bug | Redeliveries - needing validating for coordinate retrieval | 3.1.6 | 3.1.4 |
| EPOD-177 | Bug | Message processing: despatch processed after delivery | 3.1.6 | 3.1.2 |
| EPOD-179 | Bug | ETA minimum drive times between points not being applied | 3.1.5 | 3.1.4 |
| EPOD-176 | Bug | ePOD: Unexpected errors on multiple devices - Android Update | 3.1.4 | 3.1.1 |
| EPOD-174 | Issue | Uploaded photos - Server processing - using SD cards issue | 3.1.3 | 3.1.3 |
| EPOD-169 | Bug | Process uploaded images - Photos deleted when process error occurs | 3.1.3 | |
| EPOD-168 | Bug | Failed Messages - Automatic failure emails failing to send | 3.1.3 | 3.1.0 |
| EPOD-171 | Issue | Uploaded photos - Server processing | 3.1.2 | |
| EPOD-170 | Issue | EPOD Message Processing Issues | 3.1.2 | 3.1.2 |
| EPOD-167 | Bug | ETA - Calculation incorrect | 3.1.2 |
v3.1.1 (03/05/2016) |
|---|
Bug release only to fix a problem with some devices regarding the signatures not uploading. |
v3.1.0 (23/12/2016) |
|---|
| Requires Vision Distribution v1.13.0+ |
| UID | Summary | Issue Type | Affects Version/s | Description | Linked to | Custom field (Configuration Needed) | Custom field (Licensed Module) |
|---|---|---|---|---|---|---|---|
| EPOD31 | Driver 'Start Day' / 'End Day' records | New Feature | Recording of the time that the driver started and finished their day is now possible with this change. | No | No | ||
| EPOD41 | Version Check - Background change | Improvement | 1.3.1 | This process has been made more logical to simplify live system upgrades. | No | No | |
| EPOD79 | Processor service erroring when processing signature message | Improvement | 3.0.1 | An intermittent issue was noticed when processing long signature messages uploaded from EPOD. | No | No | |
| EPOD110 | Removal / cleanup of unused database objects | Issue | Background changes. | No | No | ||
| EPOD113 | Logging improvements | Improvement | A single information / error log file is recorded on each EPOD device, with this change the log has been split into two, one for the EPOD application, another for the EPOD background service with the aim to make sure log entries are never missed. | No | No | ||
| EPOD114 | SQLite Database Locked exception occurs in EPOD | Issue | An error occurred on a device whereby a manifest had the first delivery signature uploaded, but all afterwards did not, and there was no retry. Finding the cause for this has been difficult, so this issue will make changes to the back end of the application to help us in scenarios such as this. | No | No | ||
| EPOD140 | Use the Vision Live web service to retrieve post code & drive time data | New Feature | Vision EPOD will no longer need a local copy of the drive time data, instead it will receive the most up to date drive time data direct from our live web service. | No | No | ||
| EPOD141 | Repost process for failed messages | New Feature | 3.0.5 | When a message fails to process, as of 3.0.5 it's moved to a temporary location to be corrected by the support team. With this change, the support team will be able to reprocess a corrected message in a standard way for all failed messages. | No | No | |
| EPOD143 | Message processor service | Bug | 3.0.1 | When re-deliveries fail to auto create, insufficient information is currently logged about the cause of the failure, with this change we will log more information helping the support team to diagnose the issue. | No | No | |
| EPOD144 | Messages can be processed out of order causing deliveries to not be updated | Bug | 3.0.5 | Occasionally different types of ePOD messages are inserted into the message tables at the same time, if the ePOD processor is mid-way through processing then it may pick up message in the wrong order. This can cause deliveries and manifest to be updated in the wrong order, causing a delivery to be completed but still showing at a non-completed status. | No | No | |
| EPOD145 | Back end improvements for version control and automated upgrades | Improvement | Changes need to be made to the back end of the system in preparation for more automated upgrades. | No | No | ||
| EPOD151 | ETA time window storage | Improvement | Currently the exact calculated ETA is stored, we will begin to store the time window sent to customers to allow us to easily extract consistent time window information from the system in various places. | No | No | ||
| EPOD152 | Repeatedly sending the same SMS & despatch notifications not sending | Bug | A problem has been identified when SMS notifications are enabled, a delivery delay notification with a valid SMS but no valid email causes the EPOD processor to repeatedly send the same SMS over and over. During resolution of this issue it was also found that despatch confirmation SMS messages were not being sent and that has also been resolved. | No | No | ||
| EPOD153 | Wording on delayed delivery SMS | Issue | The wording in the delayed delivery SMS needs to be changed to make more sense. The new time part reads 11:30 and 12:30 instead of 11:30 to 12:30. | No | No | ||
| EPOD154 | SMS notifications with an '&' are cutting off the message | Bug | If an SMS is sent for example with 'Your delivery:X from Customer Z&Y going to CM15 0LB is scheduled for delivery on 07/07/2016' only this will be received: 'Your delivery:X from Customer Z'. | No | No | ||
| EPOD156 | Issues Found While Testing Version 3.1.0 | Issue | 3.1.0 | Issues found while testing version 3.1.0 | No | No | |
| EPOD157 | Upgrade to the latest version of the signature capture | Improvement | The signature capture screen will be upgraded to the latest version in hope of resolving some latency issues potentially caused by the older version on some devices. | No | No | ||
| EPOD158 | Sending despatch confirmation | Issue | This field was removed from the delivery screen and we are still checking it when sending despatch confirmations, it should be checking against the customer instead, in VW if linked with VW, alternatively VD. | No | No |
v3.0.6 (04/05/2016)
Update of the SMS processor to use HTTPS for more security.