Found | Scale | Resolved | Issue | Consequence |
24/11/2022 | 5 | Cost type “can duplicate” is not allowed to be changed | Once set and used, cost type “can duplicate” is not allowed to be changed for future costings. But it should be allowed to change | |
24/11/2022 | 4 | Mandatory selection of lift is not working if the booking confirmation has been saved | If the booking has been saved and is being revisited, removing the Passenger and Service lift selection when lift available is selected does not disable saving the booking, which it should | |
24/11/2022 | 4 | Bar code value printed per client | Bar code value is configurable per client but is not programmed in so the bar code always returns sales order client supplied reference, not the CargoWise S0 number | |
24/11/2022 | 2 | Categories validation results in general error | Attempts to save duplicates are not providing good user feedback. There is a general error which means changes are lost | |
24/11/2022 | 4 | Dates are saved as datetime in the bookings portal | Printed booking documents (using GMT) will show date at GMT timezone which may be different to the original local date | |
08/06/2022 | 4 | 05/07/2022 | Search not working for some bookings. | There was a glitch with the searching service meaning that some records were unable to be searched for. Cause: Regression bug. On rare occasions the search service is not updated correctly. Workaround is to export the data to Excel, look up the sales order and paste the URL with the internal booking number. Hope to be resolved by 14/06/2022. Update 14/06/2022: The search index is being rebuilt whenever necessary to allow searching. The search functionality has been fixed and is awaiting deployment in the next few days. |
08/06/2022 | 2 | 08/06/2022 | Can't look up CW1 ref using Sales Order but can be looked up using CW1 reference | CargoWise will not return results using the Sales Order reference, although the booking is loaded onto CargoWise and can be looked up by CargoWise reference number. Cause: It appears that information given to us to be passed to CW1 is not totally correct, nevertheless development team developed what was requested and bookings are loaded. Workaround is to look up the CargoWise record by CargoWise reference number, which is stored in SmartHub against each booking. Awaiting information on how this should be changed from Adam Marriott who is the technical liaison between Smart Hub and CargoWise. In the meantime requesting access to CargoWise for testing in future as the team does not have access. Update 14/06/2022: This was a user issue, nothing to do with the software. The record wasn’t being searched in the correct way. Instructions have been provided. |
31/05/2022 | 5 | 02/06/2022 | Sales orders may load incorrectly | One sales order had a missing SKU. This was fixed and deployed prior to any more being uploaded incorrectly within 2 days. Cause: Uploads were done without a “child” SKU which was correct, as previously a Parent and Child SKU were uploaded which was unnecessary by design. This showed a bug in the upload. |
31/05/2022 | 3 | 02/06/2022 | Status update not shown on Dispatched Sales Orders | When a Sales Order reached “dispatched” status the Status Update no longer showed. But it could be downloaded using the Excel export. No status information was lost. Fixed and deployed within 2 days. Cause: Regression bug. |
General
Content
Integrations