Email Command Engine — business view

1. Business Summary

Parses inbound emails containing custom commands (e.g., create PO, create RFR, auto-plan flags, plan ID) and creates the corresponding records.

2. Business Value

Frictionless intake from sales/PMs via email — no portal login needed.

3. Users / Stakeholders

PMs, AMs, sales agents.

4. Workflows

• Inbound email payload (subject, body, files) parsed.
• Tokens identified; PO/Job/RFR created accordingly; logged in a received-requests audit table.

5. Sub-Features

• Inline auto-planning toggles.
• Plan-based assignment.
• Attachment handling.

6. Business Rules

• Command keys must be present and parseable.
• Linked to email parsing templates and data-mapping templates.

7. Data Entities

Received Request, Email Parsing Template, data mapping templates.

8. Entry Points

• Inbound email.

9. Inputs & Outputs

• Inputs: emails (likely SQS-bridged).
• Outputs: PO/Job/RFR records.

10. Integrations

• Email infrastructure, ownCloud.

11. Calculations / Logic

• Parsing & validation per template.

12. Status Lifecycle

• Received Request queue states.

13. Permissions

• Authenticated by sender mapping or token.

14. Reports & KPIs

• Inbound volume, parse error rate.

15. Risks & Observations

• Command grammar is sensitive to format changes.
• Input validation must be tight to prevent abuse.

16. Source Code Evidence

• app/Controller/CommandController.php, CommandtController.php.