-
Type:
Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Links:
-
Sprint:2023.R3 New Features Sprint 4, 2023.R3 New Features Sprint 5
-
SCRUM Team:Brotherhood of Mutants
-
Story Points:1
-
Work Type Classification:Sustaining
Story
As a user, I would like to be updated when a Paid In/Out has a bad format.
Details
In the image above, the validation is triggering when a Paid In/Out has a zero dollar value. Unfortunately, I don't know all the other ways that this validation is triggered. A little research needs to be done in MxConnect to find all the validation triggers.
Fields to Validate
- PettyCashTypeId
- GlAccountNumber
- TransactionCashDepositId
- ClerkId
- Comments
- TotalAmount
AC
- There is validation that follows the MxConnect pattern (shown above) in MxNext Paid In/Out.
- This validation should trigger in MxNext in the same way as MxConnect. (See Commented List)
- Validate the fields listed in the details above
- is blocked by
-
CFAMX-25636
MxNext field validation does not trigger the same way as MxConnect
-
- Done
-
1.
|
Create Test Scripts |
|
Done | Barry Coetzee |
|
|||||||
2.
|
Review Test Scripts |
|
Done | Barry Coetzee |
|
|||||||
3.
|
Deploy |
|
Done | Barry Coetzee |
|
|||||||
4.
|
Execute Test Cases |
|
Done | Barry Coetzee |
|
|||||||
5.
|
Functional Review with QA |
|
Done | John Rust |
|
|||||||
6.
|
DIT |
|
Done | John Rust |
|
|||||||
7.
|
Design Review |
|
Done | John Rust |
|
|||||||
8.
|
Story Documentation |
|
Done | Unassigned |
|
|||||||
9.
|
Add validation and toast message |
|
Done | John Rust |
|
|||||||
10.
|
Dev Testing |
|
Done | John Rust |
|
|||||||
11.
|
Update ag-grid row color |
|
Done | John Rust |
|
