-
Type:
Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Sprint:2021.R5 CloudLink Sprint 2
-
SCRUM Team:Globogym Purple Cobras
-
Story Points:3
-
Work Type Classification:Sustaining
Currently, the CFA Polling Service checks to see if the transaction already exists in tbPolledDataTransactionHeader and then if it doesn't exists, it will add to this table and then add it to tbCFAMessage.
Originally, CloudLink was built this way to allow for extensibility but it would be far simpler to:
- Do away with check on tbPolledDataTransactionHeader
- Update tbCFAMessage to contain the columns that tbPolledDataTransactionHeader has.
- I actually think we can get away with the current columns for the duplicate check ("StoreNumer", "TransactionId", "BusinessDate")
- We can then perform the "Duplicate Check" using the table tbCFAMessage table.
- implements
-
CFAMX-14120 CloudLink - MVP
-
- Open
-
1.
|
Review Test Scripts |
|
Done | Unassigned |
|
||||||||
2.
|
Deploy |
|
Done | Unassigned |
|
||||||||
3.
|
Functional Review with QA |
|
Done | Unassigned |
|
||||||||
4.
|
DIT |
|
Done | Unassigned |
|
||||||||
5.
|
Design Review |
|
Done | Unassigned |
|
||||||||
6.
|
Remove PolledDataTransactionHeader from the duplicate check. |
|
Done | Sree Surapaneni |
|
||||||||
7.
|
Add stored procedure to use tbCFAMessage to perform duplicate check |
|
Done | Sree Surapaneni |
|
||||||||
8.
|
Create Test Cases |
|
Done | Gareth Leibbrandt (Inactive) |
|
||||||||
9.
|
Execute test cases |
|
Done | Gareth Leibbrandt (Inactive) |
|
