Company: Link Technologies
Case No: L09678. Project: 10.10: LinkSOFT Version 10.1
Logged By: Sanjay (Link Technologies) on 30 Oct 2018 10:28AM
Priority: High
Product: Point of Sale
Group: Software Defect
Time Taken: 11.00 (Weight: 11.00)
Version: 10.155.0117
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Development, Rashna, Sanjay
Resolve By: Wednesday, 24 October 2018 12:00 AM [2018 days since logged date]
Status: Closed
Subject: Forecourt Prepay Transaction Unit Price and Quantity mismatch when LinkSOFT Product price is different from Forecourt price
Summary:    Forecourt Prepay Transaction Unit Price and Quantity mismatch when LinkSOFT Product price is different from Forecourt price. 
Audit Notes:Edited by sanjay on 05/03/19 10:22. 
30 Oct 201810:28AM Comment 1 by Sanjay (Link Technologies) Case 9678 added to project 10.0
30 Oct 201810:30AM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 30-10-2018 10:30 AM Time Taken: 6.00
Development work for this case has been completed.
The change will be available in version: 10.1.0.9

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

  1. Unit price, Quantity and Line Total is based on Prepay transaction values instead of LinkSOFT Inventory values

2. The issue was caused by:

  1. The system was using LinkSOFT Inventory price to calculate quantity for prepay transactions

    3. Next Step

    1. UAT

    01 Nov 201810:32AM Comment 3 by Sanjay (Link Technologies) Assigned To: Alvis (Link Technologies) Followup Date: 01-11-2018 10:32 AM
    Assigned to Alvis for UAT

    06 Nov 201811:03AM Comment 4 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 06-11-2018 11:03 AM Time Taken: 2.00
    QA Results
    Tests carried out according to requirements specified on the case header

    Test Results Summary

    Table 1 - Summarised list of issues
    NoTest DescriptionPass/Fail
    1

    P001 - Regular - $2.50 (LINKSOFT) $0.949 (Enabler)
    P002 - Regular - $3.00 (LINKSOFT) $0.979 (Enabler)
    P003 - Regular - $0.75 (LINKSOFT) $0.549 (Enabler)



    2Process item P001 with amount as 10. Calculated quantity should be 10.53 
    Pass
    3Process item P002 with quantity as 10. Calculated amount should be 9.79
    Pass
    4Process item P003 with amount as 57.79. Calculated quantity should be 105.28
    Pass
    5receipt print values are not displayed correctly when quantity is greater than a 100. Refer to Figure 1 below.


    Figure 1: Receipt showing price been cut off.

    Recommended Change:

    1. The details section of the receipt should have 2 columns, the first to show "quantity x price description", the second to show the amount.
    2. Wrap to next line if the detail line column 1 is very long.
    3. Pad the "quantity x price" to 14 characters when "quantity x price" is less than 14 characters. This means that the product description will be aligned when "quantity x price" is less than 14 characters. 

    Environment Details

    1. OS version: Windows Server
    2. Application version: 10.1.1.2
    3. Setup: Demo
    4. Server : 10.0.0.10
    5. Database: RASHNA-LINKSOFT-DEMO-10

    Steps to reproduce failed scenarios:

    Next Step: for correction

    Thanks
    Sanjay and Rashna


      07 Nov 201801:59PM Comment 5 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 07-11-2018 01:59 PM Time Taken: 2.00
      Development work for this case has been completed.
      The change will be available in version: 10.1.1.3

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

      1. The requested design of adding character padding is not possible as the font is not fixed width. An alternative option is to display each line in 2 rows. 1st row contains the product description and 2nd-row having quantity, price and amount.
      2. For now, I have added "can grow" option to "quantity x unit price" field. This will wrap the "quantity x price" field to 2nd line if it does not fit.

      2. The issue was caused by:

      1. N/A

        3. Next Step

        1. UAT

        08 Nov 201808:46AM Comment 6 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 08-11-2018 08:46 AM Time Taken: 1.00
        Hi Sanjay
        QA Results
        Tests carried out according to requirements specified on the case header

        Test Results Summary

        Table 1 - Summarised list of issues
        NoTest DescriptionPass/Fail
        1Process a sale of P001 with the amount as 266. Validate that quantity and unit price is clearly visible in the receiptPass
        2Process a sale of P001 with the quantity as 350. Validate that quantity and unit price is clearly visible in the receipt
        Pass

        Figure 1: Receipt Sample

        Environment Details

        1. OS version: Windows Server 2012
        2. Application version: 10.1.1.3
        3. Setup: Demo
        4. Server : 10.0.0.10
        5. Database: RASHNA-LINKSOFT-DEMO-10

        Steps to reproduce failed scenarios: N/A

        Next Step: for closure


          08 Nov 201808:47AM Comment 7 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 08-11-2018 08:47 AM
          Thanks Rashna

          09 Oct 201908:14AM Comment 8 by Sanjay (Link Technologies) Quality control status: Pass. QC Not required - This case was created before quality check was implemented in version 11 on 30/06/2019
          If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L09678 in the subject line of all emails regarding this issue.

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