| Subject: | Last Mileage Edited at HQ is not reflected at all branches |
| Summary: | We have identified that when an incorrect higher mileage is entered, they need to correct this by entering the lower mileage.
To correct this, they are editing the last mileage at HQ. In doing so, this last mileage is only sent to the site where this transaction originated from and not all the sites.
This is because we have the replication rule enabled to "restrict data travelling to all configured locations only".
To resolve this issue, we will need to add the last mileage in the fleet maintenance and enhance the mileage check functionality to review the last mileage rather than the POS Order Detail table
Test case:
- Set up 2 branch sites.
- Create a new fleet with mileage mandatory
- Perform transaction at Branch 1 with Mileage as 450
- Now perform the transaction at Branch 2, and try entering a lower mileage. This should not be permitted
- Turn off Mileage Mandatory for a fleet and enter the higher mileage at Site 1.
- Enable Mileage Mandatory and go to Branch 2. Enter actual mileage lower than mileage entered in (5) above. The system should prompt low mileage prohibited messages.
- Now correct mileage at HQ and try performing the sale from Branch 2 again. The system should allow processing this mileage now.
|
| Audit Notes: | Edited by sanjay on 26/09/22 09:58. Edited by sanjay on 11/09/22 13:50. Edited by sanjay on 11/09/22 13:50. Edited by sanjay on 15/08/22 10:42. Edited by sanjay on 15/08/22 10:42. Edited by sanjay on 18/07/22 14:39. Edited by sanjay on 25/03/22 15:15. Edited by sanjay on 18/02/22 10:22. |
| 04 Dec 2021 | 10:13AM Comment 1 by Sanjay (Link Technologies) Assigned To: Vineet (Link Business Solutions) Followup Date: 06-12-2021 02:12 PM Time Taken: 1.00 |
| Hi Vineet, bring this case to a meeting so we can discuss it. Also, please cleanup the case and format it so it is clear to follow. |
|
| 18 Feb 2022 | 10:22AM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 18-02-2022 02:22 PM Time Taken: 1.00 |
| Closing this case dud to no response. |
|
| 25 Mar 2022 | 03:17PM Comment 3 by Sanjay (Link Technologies) Assigned To: Vineet (Link Business Solutions) Followup Date: 25-03-2022 07:15 PM Time Taken: 1.00 Notes: Edited by sanjay on 26/09/22 09:59. |
| Development Notes:- Add a LastMileage field at the Vehicle Maintenance form as the Order Header is not replicated to all branches
- Change Vehicle Mileage to validate based on Vehicle Table instead of Order Header
- Add LastMileage to Vehicle Replication
|
|
| 18 Jul 2022 | 10:02AM Comment 4 by Vineet (Link Business Solutions) This comment has been removed |
| 18 Jul 2022 | 02:37PM Comment 5 by Sanjay (Link Technologies) Case L12649 added to project 14.01 |
| 27 Jul 2022 | 12:38PM Comment 6 by Vineet (Link Business Solutions) This comment has been removed |
| 27 Jul 2022 | 04:55PM Comment 7 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 31-08-2022 08:54 PM Time Taken: 1.00 Notes: ETC extended from: 30/11/2021 to 31/08/2022 |
| Added to project 14.01 |
|
| 11 Sep 2022 | 02:59PM Comment 8 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 14-09-2022 05:50 PM Time Taken: 18.00 |
| PART A - Development work for this case has been completed. 1. The change will be available in version:14.10 2. The following changes were made(Include Database object names, Program classes, and any other relevant information): - Added to fields on CustomerFleet Table. LastMileage and LastMileageDate.
- Changed Validation to use Customer Fleet table instead of Transaction Table
- Changed the "Vehicle Mileage UPDATE" form (Menu: "Point of Sale ~> Customer Profile ~> Vehicle Mileage") to get the highest mileage and update the summary table
- Changed Replication to send the summary fields in Replication
3. Affected Areas: - Vehicle Mileage Operation including Updates and Validation
4. The issue was caused by: - Improvement/Change Request
5. Other Relevant Notes:
6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT
|
|
| 05 Oct 2022 | 11:21AM Comment 9 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 14-10-2022 10:24 AM Time Taken: 18.00 |
|
The following tests were performed:
Test Setup Instructions: - Create a Replication Environment. HQ, BA, BB as three servers
- ENABLE replication RULE R0100
- Configure Replication Locations to prevent data from Branch BA to flow into BB
- Create Two Fleet Vehicles IN HQ and Three Fuel Products in HQ
- Ensure user ADMIN does not have access to Override Mileage data
Table 1 - Test Results
| No | Test Case | Expected Result | Pass/Fail | Comments | | 1 | Create a Fleet Sales in BA. Set Mileage to 1000. Compete Sale
| All branches should get the Mileage data. Branch BA should not get transactional data
| Pass
|
| | 2 | Create a Fleet sale in BB, and set mileage to 900. Complete Sale
| The sale should require Override authorisation
| Pass
|
| | 3 | Change mileage to 1010 in 2 above and complete sale
| The sale should not require authorisation. The authorisation should allow SAVE
| Pass
|
| | 4 | EDIT Mileage in BA, reduce Mileage to 900
| Mileage should transfer to all locations
| Pass
|
| | 5 | Perform Sale using new reduced Mileage in 4. above
| Sale should continue without override authorisation
| Pass
|
|
Environment Details - OS version: Win11
- Application version: 14.10 BETA4
- Setup on:
- Server: LinkQA4
- Database: LinkSOFT
- LinkSOFT URL: HTTP://LinkQA4/LinkSOFT
- Login Details: Standard username and password for user "admin"
Next Step: Closure
|
|