-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: CFA 2020R2
-
Component/s: CollectedSales
-
Labels:
-
Sprint:CFAMX 2020R2 Sprint 1
-
SCRUM Team:Brotherhood of Mutants
-
Story Points:5
-
Work Type Classification:Sustaining
As an operator I want to be able to select multiple customers when allocating a collected sale so that I can split the payment
Notes
- Per our meeting on 1/3, this builds on the work already done by David Nayyar
- Overview:
- Move the Customer details (Account/Balance) into the same header as the Collected Sale Detail
- Split the header into two sections (Customer details/Collected Sales details)
- After selecting Actions > Split Payment, select a customer, and display the details for that customer
- The customer name becomes a drop down, used to toggle between customers
- Doing this allows us to keep the standard grid control (with pagination, think 01919 DoorDash)
- In addition to the different customers, also provide filters for:
- Applied Payments
- All Customers
- In these views, display the customer name as the first column and in Portrait mode display it in the Invoice Details, in the Right Hand Panel
- For example:
- Customer 1
- Customer 2
- Applied Payments Only
- All Invoices
- Remove the Customer Details section in the right hand panel, the customer name and balance will just be a row in the Invoice Details when either the Applied Payments or All Customers filter is selected
- As discussed on 1/9/20 with Michael DeBinder & Soma Dixon - When the Apply Payment page is displayed, if the Collected Sale has transactions for multiple customers, display details for the selected customer, and also list the other customers so that the user knows which customers the Collected Sales has been already split between.
Acceptance Criteria
- Confirm that there is an option under Actions to Split Payment
- Confirm that after selecting Split Payment the user is prompted to select a customer
- Confirm that customers that are already selected are not available for selection again
- Confirm that the customer name and balance are displayed on the page once selected
- Confirm when a customer is selected the TBCs displayed are for that customer
- Confirm that if there are no TBCs for that customer, that a message is displayed informing the user of this
- Confirm when switching between customers the TBC details change
- Confirm that the Collected Sales details are updated as TBC's are selected for multiple customers
- Confirm that there is a filter that allows the user to view All TBC's that have been selected for Apply Payments
- Confirm when the Apply Payment filter is selected all TBC's that are marked to Apply are displayed, and that others are not displayed
- Confirm that there is a filter to display All Customers that the user has selected
- Confirm when the All Customers filter is selected, TBC's are displayed for all Customers that have been selected in the Split Payment Process
- Confirm that after selecting at least one TBC, the option to Apply Payment is available under actions and allows the user to apply the payment
- Note: Credit and Paid Out will be covered under a different story
- implements
-
CFAMX-5958 CM - Collected Sales - MxC - Re-write & redesign the Collected Sales Page in MXC
- Closed
- is implemented by
-
CFAMX-8336 Collected Sales - Multi Browser Scenarios
- Closed
-
CFAMX-7744 Create Test Cases
- Done
- is related to
-
CFAMX-7791 Collected Sales - Split Payment IPAD UI work
- Closed
-
CFAMX-7814 2020.R2(S1): Customer Balance does not reduce by the sum of the checked invoices
- Done
-
CFAMX-7836 2020.R2(S1): Split Payment - Applied Column Sort is not working
- Done
-
CFAMX-7790 2020.R2(S1):Split Payment - Customers with Credit or NO TBCs do not *Initially* get the Credit option
- Done
-
CFAMX-7796 2020.R2(S1): Collected Sales page-Invoices are not checked on the next page when Payment amount is greater than multiple invoices
- Done
-
CFAMX-7815 2020.R2(S1):Collect Sale-Age of Invoices are not correct on the details panel
- Done
1.
|
Review Test Scripts | Done | Gareth Leibbrandt (Inactive) |
|
|||||||||
2.
|
Deploy | Done | Soma Dixon (Inactive) |
|
|||||||||
3.
|
Functional Review with QA | Done | Soma Dixon (Inactive) |
|
|||||||||
4.
|
DIT | Done | Michael DeBinder (Inactive) |
|
|||||||||
5.
|
Take UI Mockups, add tweaks and merge | Done | Michael DeBinder (Inactive) |
|
|||||||||
6.
|
Create Test cases | Done | Soma Dixon (Inactive) |
|
|||||||||
7.
|
Execute Test Cases | Done | Soma Dixon (Inactive) |
|