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

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: