-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Won't Develop
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Exports
-
SCRUM Team:Brotherhood of Mutants
-
SOW (Time Tracking) Project:44918
-
Work Type Classification:Sustaining
Duplicate of CFAMX-3638
***************************
As a store manager I want to be prompted to fix Incomplete TBC transactions as a part of my daily workflow so that I do not have to log a support ticket at month end
Notes:
- Build off/key off the logic implemented in
CFAMX-4277 - When an incomplete TBC is received for a finalized day, the next time the user goes to the TBC page they should be prompted:
- Inform the user that they have to fix data on an old day (popup) before they can complete the current day
- Take the user to the correct day that needs data fixing
- After fixing the day, and assuming Paid In/Outs are good for that day, queue the PMix and CDS exports
- If there are subsequent days that need fixing between the day last fixed, and the current open business day, take the user to that day
- Once all old days are fixed, let the user complete the current open business day
Acceptance Criteria
- Confirm that there is no detrimental impact on the loading of the TBC page to support this functionality
- Confirm that the user is informed that they need to fix data on an older day than the current business day
- Confirm that the user can fix data on a day that is finalized
- Confirm that those TBC transactions that were complete when the day was finalized, cannot be edited
- Confirm that after fixing the data, messages are queued to validate Paid In/Out's and then run the CDS and PMix Exports
- Confirm when data for old days is fixed, the user can complete the current business day
- implements
-
CFAMX-4492 TBC - R4 - Re-write & redesign the TBC/Outside Sales in MXC
- Closed
- relates to
-
CFAMX-3015 Automate File Export when Sales After Finalized Day are Taken
- Closed