-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: CFA 2022R2
-
Component/s: None
-
Labels:
-
Sprint:2022.R2 New Features Sprint 4, 2022.R2 New Features Sprint 5, 2022.R3 New Features Sprint 1
-
SCRUM Team:Brotherhood of Mutants
-
Story Points:3
-
Work Type Classification:Sustaining
We need to update the CFA Message Processor to handle transactions that have been Cancelled
This is different to 1 or 2 items that cancelled from within a transaction of say 10 items. (These get logged as Deletions Before/After)
In Radiant TLD we would check the "status" property of a transaction. We don't seem to have that in the new JSON files.
An example of a completely cancelled transaction can be found here: Cancelled Transaction.json
Busy sending an email to Timothy Chase and Harrison Sloan regarding this "status" field.
An alternative solution might be to:
- check the cancelAfterTotalCount property
- check this against the number of orderLines
OR
Create a property on the Transaction class to check if ALL the orderLines "cancelStatusCode" property is something other than 0, then consider the whole transaction cancelled.
A whole transaction that has been cancelled looks like this (Radiant TLD XML)
- implements
-
CFAMX-14120 CloudLink - MVP
- Open