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.