TBC > Previous Days Invalid Entry Message

As an Operator, I would like to be prompted for any previous days TBC sale transactions that require action when entering the To Be Collected page on a mobile device.

Detail

• Context - There is a recurring issue that happens in Production that the HS Support Desk has to action to resolve, and this story is to help operators fix the issue themselves! Operators take POS systems to other locations, and bring them back onto the network days after the transactions/event happened, when this occurs, and a TBC is uploaded that requires action, for a day that has been finalized, Support have to go in and reopen past days. The goal of this story is to prompt/inform the user that they have data from past days that needs to be corrected before resolving the current day
  • TBC's are resolved as a part of the workflow, and when accessed through the workflow, the user is completing a specific business date.
  • If for example the user is completing the workflow for 5/18, but a TBC is uploaded (that requires action) for 5/16, the user should be taken to the business date of 5/16 and be prompted to take action prior to completing the workflow for 5/18.
• Provide a mechanism for a user to action multiple TBC's for past (finalized business dates)

HLE Notes
Make sure we run performance tests. Look into query running for multiple days versus a single day.

Acceptance Criteria:

1. Confirm when TBCs are uploaded for previous days, and the user is completing the most recent workflow, when going to the TBC task the user is prompted to resolve them prior to completing the current business date
   • This is similar to what we are doing the Paid In/Out
2. Confirm that the user is notified that they are being asked to correct data for past dates
3. Confirm that the data for past dates must be resolved before the user can advance the date to the current date
4. TBC uploaded without a customer, customer must be assigned to TBC
5. Confirm that the check for TBC's for prior days goes back at least 35 days (1st day of the currently open period including the 5 day grace period)
6. ^New Confirm the check for TBC's goes back to the first day of the month the workflow instance is currently on (Same validation currently used for PaidIn/PaidOut).
7. Confirm the CDS and PMix Exports are queued and exported for the day, after the TBC is fixed (CFAMX-4287)