| # | Title | Description | Notes |
|---|
| 1 | Report Layout | The system will generate an excel file with the fields detailed in the "File Format and Details" section of this document | - Must generate as a valid XSLX formatted file
|
| 2 | Report Content | The system will include the distinct information details outlined in the "Report Definition" below for any application imported into the LapMgr system during the previous month regardless of the applications current status. Applications handled in the PreApp (paper apps/updates) will not be included. |
|
| 3 | Report Content | The system is not expected to exclude applications from the list by any means other than the Import Date |
|
| 4 | Report Content | Any field which does not contain a value in the LapMgr database will be listed as an empty field in the output file |
|
| 5 | Report Delivery | The system will deliver the generated file via email using an email as defined in the Email Definition section of this document. |
|
| 6 | Report Recipients | The system will be able to deliver the report to one or more recipients. Changes to the recipients must not require code changes | Initial recipient list is: Kim Philips, Keeley Cook, Jami Soedler, Dave Ryzcko |
| 7 | Report Generation | The system will generate the report on a monthly basis via a scheduled task. |
|
| 8 | Report Generation | The system is not expected to retain a copy of the generated report once it has been sent. |
|
| 9 | Error Handling | The system will be expected to provide a detailed log of any errors encountered during the creation of the report, email or its delivery | *Delivery issues up to and including the handoff to the ASWB mail system. This will not include reporting/logging of bounce back or other delivery failures that result from the recipients mailbox |
| 10 | Monitoring | The system will immediately notify IT staff (to the extent it is possible) of any failures or errors encountered with the the report creation and email process. |
|