Schedule Reports & Scheduled Emails

Business perspective: Scheduled Reports & Aggregations

1. Business Summary

Aggregations and scheduled email reports (e.g., accounts_resources daily snapshot).

2. Business Value

Routine management reporting and audit snapshots.

3. Users / Stakeholders

Managers, executives.

4. Workflows

  • Cron #34 accounts_resources() populates accounts_resources table by aggregating tasks per account/resource/skill/language.
  • logCron records each run.
  • Various cron actions email scheduled reports to recipients.

5. Sub-Features

  • ScheduleReport / ScheduleReportLog.

6. Business Rules

  • Recipients configured per report.
  • Logged for audit.

7. Data Entities

ScheduleReport, ScheduleReportLog, accounts_resources.

8. Entry Points

  • schedule_reports/* cron.

9. Inputs & Outputs

  • Inputs: schedule definition, source data.
  • Outputs: aggregated tables, emailed reports.

10. Integrations

  • Email.

11. Calculations / Logic

  • Aggregations across multiple tables.

12. Status Lifecycle

  • Run states logged.

13. Permissions

  • Internal cron.

14. Reports & KPIs

  • Operational utilization snapshots.

15. Risks & Observations

  • Long-running aggregates may impact DB performance.

16. Source Code Evidence

  • app/Controller/ScheduleReportsController.php (~3,192 LOC).
  • app/Model/ScheduleReportLog.php.

← Deep dives index