Company: Link Technologies
Case No: L12838. Project: 14.70: LinkSOFT Version 14.70 - May 2023
Logged By: Vineet (Link Business Solutions) on behalf of Sanjay (Link Technologies) on 06 Feb 2023 12:07PM
Priority: Low
Product: Point of Sale
Group: Enhancement
Time Taken: 9.00 (Weight: 12.00)
Assigned To: Development
Circulation: Development, Sanjay, Vineet
Resolve By: Friday, 28 April 2023 01:47 PM [436 days since logged date]
Status: Closed
Subject: Add Additional Purchase Details to Customer Fleet Transaction Listing Report
Summary:    

With reference to the case, L12589 Add Additional Purchase Details to Customer Fleet Transaction Listing Report, since additional information was discussed on skype and not recorded in the case, the report design did not meet the customer need.

Non-Fleet transaction means items purchased without using a customer fleet card. For these items, cashiers enter's the Purchase Order Number (PO No#). These PO No#s are recorded in Table : LBS_POS_Order Column: Field1. Similar to Customer Fleet Statement Report, we need to add the Non-Fleet Transactions in the Customer Fleet Transaction Listing Report.

Figure 1.1. Report Sample Customer Fleet Transaction Listing


Audit Notes:Edited by sanjay on 19/04/23 15:43. Edited by sanjay on 18/04/23 11:46. Edited by sanjay on 30/03/23 09:46. Edited by sanjay on 20/03/23 16:39. Edited by sanjay on 20/03/23 16:38. Edited by sanjay on 15/03/23 13:41. Edited by sanjay on 10/03/23 08:35. 
06 Mar 202302:42PM Comment 1 by Vineet (Link Business Solutions) Assigned To: Development Followup Date: 08-03-2023 06:15 PM Time Taken: 1.00

Discussion between Vineet and Sanjay 06/03/2023

  1. This report should show "All" transactions for the filters shown. At the moment this report only shows transactions where fleet cards have been scanned.
  2. Add the following rules:
    1. Show All Transactions including transactions added outside the fleet card scan Y|N. 
    2. Use Fleet Card scan to identify Fleet Transactions: Y|N

10 Mar 202308:35AM Comment 2 by Sanjay (Link Technologies) Case L12838 added to project 14.60
20 Mar 202304:38PM Comment 3 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 22-03-2023 08:37 PM
Moved to 14.70 due to urgent release with bug fixes in 14.50

20 Mar 202304:38PM Comment 4 by Sanjay (Link Technologies) Case L12838 added to project 14.70
30 Mar 202310:59AM Comment 5 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 28-04-2023 01:47 PM Time Taken: 6.00 Notes: ETC extended from: 09/02/2023 to 28/04/2023
PART A - Development work for this case has been completed.

1. The change will be available in version: 14.70

2. The following changes were made(Include Database object names, Program classes, and any other relevant information):

  1. Added POS Order Header Notes in Fleet Transaction Report.
  2. Order notes are added based on the configuration of each POS Order Header Field. E.g. If "POSOrder.Field1" is configured for "PO Number" and "POSOrder.Field2" is configured for "Mobile Number", both Fields will appear with their respective tags. If all four fields are configured, all four fields will appear with their field tags.
  3. Data is displayed under the Driver details. We could not fit this under Mileage as requested. See figure 1 for details.

3. Affected Areas:

  1. Fleet Transaction Listing Report

4. The issue was caused by:

  1. Enhancement Request

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

Figure 1 - Changes to Fleet Transaction Listing Report