Company: Link Technologies
Case No: L12649. Project: 14.10: LinkSOFT version 14.10 - October 2022
Logged By: Vineet (Link Business Solutions) on behalf of Sanjay (Link Technologies) on 29 Nov 2021 11:06AM
Priority: Low
Product: Point of Sale
Group: Enhancement
Time Taken: 40.50 (Weight: 40.50)
Assigned To: Development
Circulation: Development, Sanjay, Vineet
Resolve By: Friday, 30 September 2022 12:00 AM [871 days since logged date]
Status: Closed
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:

  1. Set up 2 branch sites.
  2. Create a new fleet with mileage mandatory
  3. Perform transaction at Branch 1 with Mileage as 450
  4. Now perform the transaction at Branch 2, and try entering a lower mileage. This should not be permitted
  5. Turn off Mileage Mandatory for a fleet and enter the higher mileage at Site 1.
  6. 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.
  7. 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 202110: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 202210: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 202203: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:
  1. Add a LastMileage field at the Vehicle Maintenance form as the Order Header is not replicated to all branches
  2. Change Vehicle Mileage to validate based on Vehicle Table instead of Order Header
  3. Add LastMileage to Vehicle Replication

18 Jul 202210:02AM Comment 4 by Vineet (Link Business Solutions) This comment has been removed
18 Jul 202202:37PM Comment 5 by Sanjay (Link Technologies) Case L12649 added to project 14.01
27 Jul 202212:38PM Comment 6 by Vineet (Link Business Solutions) This comment has been removed
27 Jul 202204: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 202202: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):

  1. Added to fields on CustomerFleet Table. LastMileage and LastMileageDate. 
  2. Changed Validation to use Customer Fleet table instead of Transaction Table
  3. Changed the "Vehicle Mileage UPDATE" form (Menu: "Point of Sale ~> Customer Profile ~> Vehicle Mileage") to get the highest mileage and update the summary table
  4. Changed Replication to send the summary fields in Replication

3. Affected Areas:

  1. Vehicle Mileage Operation including Updates and Validation

4. The issue was caused by:

  1. Improvement/Change Request

5. Other Relevant Notes
6. Next Step
(Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT


05 Oct 202211: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:
  1. Create a Replication Environment. HQ, BA, BB as three servers
  2. ENABLE replication RULE R0100
  3. Configure Replication Locations to prevent data from Branch BA to flow into BB
  4. Create Two Fleet Vehicles IN HQ and Three Fuel Products in HQ
  5. Ensure user ADMIN does not have access to Override Mileage data
Table 1 - Test Results
NoTest CaseExpected ResultPass/FailComments
1Create 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

2Create a Fleet sale in BB, and set mileage to 900. Complete Sale
The sale should require Override authorisation
Pass

3Change mileage to 1010 in 2 above and complete sale
The sale should not require authorisation. The authorisation should allow SAVE
Pass

4EDIT Mileage in BA, reduce Mileage to 900
Mileage should transfer to all locations
Pass

5Perform Sale using new reduced Mileage in 4. above
Sale should continue without override authorisation
Pass

Environment Details

  1. OS version: Win11
  2. Application version: 14.10 BETA4
  3. Setup on:
    1. Server: LinkQA4
    2. Database: LinkSOFT
    3. LinkSOFT URL: HTTP://LinkQA4/LinkSOFT
  4. Login Details: Standard username and password for user "admin"

Next Step: Closure


If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L12649 in the subject line of all emails regarding this issue.

Document size: 14.2 KB
For call complaints, please contact the Managing Director of the company using this form