Real-World Example
Maya needs a one-time report for last month. She chooses Notice Responses, selects the start and end dates, and downloads the CSV. The portal limits the date range so a one-time report cannot accidentally request too much data.Visual Flow
Report Types
Notice Response Report Statuses
Notice response reports should export both sender classification and response lifecycle status.
The UI often shows the sender classification as
AM, PM, YP, or CP, but notice-response CSV exports use the full labels.
How It Should Work
- It should require report type, start date, and end date.
- It should reject future dates.
- It should require the end date to be on or after the start date.
- It should limit one-time report ranges to two months.
- It should download CSV only when matching records exist.
How It Should Not Work
- It should not generate reports with unbounded date ranges.
- It should not silently return an empty CSV as a successful report.
- It should not mix report types in one file.
Developer Notes
- Dates are interpreted using EST and converted for the report query.
- The report type enum controls the allowed report list.
- Notice-response export mapping keeps creditor member/profile status separate from creditor response status.
Related App Areas
app/Livewire/ConsumerResponseManager/Reports/GenerateReport/IndexPage.phpapp/Livewire/ConsumerResponseManager/Forms/GenerateReportForm.phpapp/Livewire/ConsumerResponseManager/Traits/NoticeResponseGenerateReport.phpapp/Enums/NoticeResponseReportType.phpapp/Exports/ConsumerResponseManager/NoticeResponseExport.phpapp/Exports/ConsumerResponseManager/NoticeResponsesExport.php