-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Sprint:2022.R3 New Features Sprint 2
-
SCRUM Team:Brotherhood of Mutants
-
Story Points:3
-
Work Type Classification:Sustaining
Details
- A TBC is tendered on the POS, with a customer selected
- The TBC is processed by InFORM
- When the user views the TBC page the TBC is displayed
- A collected sale is tendered on the POS for the same customer
- The collected sale is processed by InFORM
- The user applies the Collected Sale to the TBC
- A TBC Refund is tendered on the POS, with a customer selected
- The TBC Refund is processed by InFORM
- On the TBC page the Refunded TBC must be resolved in order to complete the TBC process for the day
- In this case, resolved means that the Collected Sale is unapplied
- The TBC is locked, and it is indicated that the TBC was refunded
- Actions to resolve:
- User goes to Collected Sale page
- The user unapplies/unallocates the Collected Sale from the TBC
- Once the collected sale is no longer linked to the TBC, the TBC becomes unlocked and can be deleted
- Delete action is available under this condition
- When the CDS is generated for the day, neither the TBC nor the Refund are included in the export file
AC
- When a TBC is associated to a Collected Sale and the TBC is later refunded that the user cannot update any of the details of the TBC (Account Name, Invoice #, Description)
- When a TBC is associated to a Collected Sale and the TBC is later refunded, that it is indicated on the TBC page that the TBC is locked and has an associated refund
- When the the TBC and Collected Sale are no longer linked that the TBC/Refund is no longer linked and is available to be deleted
- The delete process is documented
- The TBC/Refund can be deleted
- implements
-
CFAMX-12484 InFORM Angular Technology Update
- In Development
1.
|
Create Test Scripts | Done | Tristan Strong |
|
|||||||||
2.
|
Review Test Scripts | Done | Unassigned |
|
|||||||||
3.
|
Deploy | Done | Tristan Strong |
|
|||||||||
4.
|
Execute Test Cases | Done | Tristan Strong |
|
|||||||||
5.
|
Functional Review with QA | Done | Sree Surapaneni |
|
|||||||||
6.
|
DIT | Done | Sree Surapaneni |
|
|||||||||
7.
|
Design Review | Done | Sree Surapaneni |
|
|||||||||
8.
|
Story Documentation | Done | Sree Surapaneni |
|
|||||||||
9.
|
Add label when there is a refund associated to a collected sale | Done | Sree Surapaneni |
|
|||||||||
10.
|
Dev Testing | Done | Sree Surapaneni |
|
|||||||||
11.
|
Implement Refund Delete | Done | Sree Surapaneni |
|