Company: Link Technologies
Case No: L12201. Project: 12.30: LinkSOFT Version 12.30
Logged By: Sanjay (Link Technologies) on 19 Mar 2021 11:20AM
Priority: High
Product: Framework
Group: Software Defect
Time Taken: 13.50 (Weight: 13.50)
Version: 12.32
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Rashna, Sanjay
Resolve By: Friday, 26 March 2021 12:00 AM [1125 days since logged date]
Status: Closed
Subject: Integration Transactions that come through the API that is DUPLICATES are not created in LinkSOFT
Summary:    

Integration Transactions that come through the API that is DUPLICATE are not created in LinkSOFT. We do this as we do not handle duplicate transactions.

Solution:  If a duplicate entry comes through the API, we do the following:

  1. If the Status of the previous entry is "FAILED" or "ERROR", we mark this as "Deleted - Duplicate ENtry Received" and create the new entry. This is because the entry may have failed TIMS or further processing and the API required to resend this.
  2. If the status is "CLOSED" or "Processing", we do not create  the entry, and we log a validation message with the transaction details
Audit Notes:Edited by sanjay on 24/03/21 11:21. Edited by sanjay on 19/03/21 11:20. 
19 Mar 202111:22AM Comment 1 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 19-03-2021 03:20 PM Time Taken: 12.00

PART A - Development work for this case has been completed.

1. The change will be available in version:12.32.0319

2. The following changes were made(Include Database object names, Program classes, and any other relevant information): Changed SQL API to handle duplicate entries as follows:

  1. If the Status of the previous entry is "FAILED" or "ERROR", we mark this as "Deleted - Duplicate ENtry Received" and create the new entry. This is because the entry may have failed TIMS or further processing and the API required to resend this.
  2. If the status is "CLOSED" or "Processing", we do not create  the entry, and we log a validation message with the transaction details

3. Affected Areas:

  1. SQL API Integration Import

4. The issue was caused by:

  1. Previously we were not handling Duplicates

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

----------------------

PART B - Development Reference (Place descriptor for objects changed):

1. Changes implemented was according to the approved design (Y/N):

2. Other relevant notes:


24 Mar 202102:20PM Comment 2 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 24-03-2021 07:51 PM Time Taken: 1.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
1Integrate a transaction from SQL API and sign it with TIMSPass
2Integrate a transaction from SQL API that has missing tax labels. The system will mark this as failed.Pass
3Correct the missing tax labels in LinkSOFT and submit them for signing. The system should sign and send the success details to SQL API. Check the SQL API has received this information.Pass
4Correct the missing tax label in the external system and reimport these via SQL API. The failed transaction should be marked as "Deleted - Duplicate" and a new transaction is created for signing.Pass
5Reimport a closed transaction from SQL API, the system should not create a new transaction. Check logs and confirm.Pass

Environment Details

  1. OS version: Windows Server 2012
  2. Application version: 12.32.0324BETA
  3. Setup: Demo
  4. Server : 10.0.0.16
  5. Database: LINKSOFT

Next Step

  1. For Review

    29 Mar 202101:53PM Comment 3 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 29-03-2021 07:46 PM Time Taken: 0.50
    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
    1Verify case for closurePass

    Environment Details

    1. OS version: Windows Server 2012
    2. Application version: 12.30.0325BETA
    3. Setup: Demo
    4. Server : 10.0.0.14
    5. Database: LINKSOFT

    Next Step

    1. For Closure

      06 Apr 202101:15PM Comment 4 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 06-04-2021 07:12 PM
      Thanks Rashna

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

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