-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Sprint:2023.R1 New Features Sprint 3
-
SCRUM Team:Brotherhood of Mutants
-
Story Points:5
-
Work Type Classification:Sustaining
Story
Details
- cfahome.com/M2/Financial/PaidInOut
AC
Confirm and compare the MxConnect and MxNext pages
- The page header is labeled correctly
- When there are No Records, the pages match
- There is a Add Reimbursement and Add New Record Button
- When the user selects Add New Record, they are asked to select Type, Category, Cashier, Description, and Amount.
- Type = Dropdown of Types
- Category =Dropdown of Categroies
- Cashier = Dropdown of Cashiers
- Description = Free Text field
When the user selects "Add Reimbursement"Type (Text only. No Dropdown) = Defaulted to "Paid Out"Category (Text only. No Dropdown) = Defaulted to "To Be Reimbursed"Cashier = Selectable dropdown of CashiersDescription = Free Text fieldAmount = Currency fieldFor this specific option, the user is asked to "Select Department" and "Select Subject". No other category includes these additional selections.
- When records exists the user can edit or delete the record
- The Confirm Delete modal is triggered when the user attempts to delete
The To Be Reimbursed category in existing records includes a clickable icon that presents the user with additional info including the "Department" and "Subject". This additional info bubble is labeled and formatted correctly.- If the user attempts to navigate away while editing a record or reimbursement, the dirty guard modal is triggered.
- This modal is formatted correctly.
- Clones
-
CFAMX-22434 MxNext Cash Management UI - Collected Sales (6) Exists in MxNext
- Closed
- implements
-
CFAMX-12484 InFORM Angular Technology Update
- In Development
- Is Clone Of
-
CFAMX-22452 MxNext Cash Management UI - Cashier Settlement (8)
- Closed
1.
|
Create Test Scripts | Done | Gareth Leibbrandt (Inactive) |
|
||||||||
2.
|
Review Test Scripts | Done | Unassigned |
|
||||||||
3.
|
Deploy | Done | Gareth Leibbrandt (Inactive) |
|
||||||||
4.
|
Execute Test Cases | Done | Gareth Leibbrandt (Inactive) |
|
||||||||
5.
|
Functional Review with QA | Done | Christiaan Badenhorst |
|
||||||||
6.
|
DIT | Done | Christiaan Badenhorst |
|
||||||||
7.
|
Design Review | Done | Christiaan Badenhorst |
|
||||||||
8.
|
Story Documentation | Done | Christiaan Badenhorst |
|
||||||||
9.
|
Adding UI components | Done | Christiaan Badenhorst |
|
||||||||
10.
|
Add date picker | Done | Christiaan Badenhorst |
|
||||||||
11.
|
Add Api calls and bind the data | Done | Christiaan Badenhorst |
|
||||||||
12.
|
Dev Testing | Done | Christiaan Badenhorst |
|
||||||||
13.
|
Include confirmation check for workflow date | Done | Christiaan Badenhorst |
|
||||||||
14.
|
Fix Defects | Done | Christiaan Badenhorst |
|