Content Checker Alerts — business view
Technical trace: Content Checker Alerts
1. Business Summary
Manages a queue of alerts triggered by content events on accounts/jobs/opportunities; processes pending alerts and routes them to the right reviewers.
2. Business Value
Surfaces compliance and quality alerts to the right people quickly.
3. Users / Stakeholders
Operations, compliance, brand managers.
4. Workflows
- Pending alerts processed by cron.
- Routing varies by entity type (Account/Job/Opportunity).
- Recipients resolved via security tables.
- Status: pending → processing → sent or error.
5. Sub-Features
- Alert queue, status flags, per-entity routing.
6. Business Rules
- Entity-type branching defines viewer logic.
- Errors retained as a non-final state.
7. Data Entities
Content Checker Alert.
8. Entry Points
- Content checker cron.
9. Inputs & Outputs
- Inputs: pending alerts.
- Outputs: emails/alerts to viewers.
10. Integrations
- Email/messaging.
11. Calculations / Logic
- Status state machine.
12. Status Lifecycle
- Pending → processing → sent/error.
13. Permissions
- System cron.
14. Reports & KPIs
- Alert volume, error rate.
15. Risks & Observations
- Hard-coded entity branching limits extensibility.
16. Source Code Evidence
app/Controller/ContentCheckerController.php.