Auto Emails
Overview
Section titled “Overview”Frappe DocType Auto Emails (Lee Kim Alliance ERP).
- Category: Automation & communications
- Module folder:
lee_kim_alliance_erp - Submittable: No
- Track changes: No
Source files
Section titled “Source files”- JSON:
leekimerp/lee_kim_alliance_erp/doctype/auto_emails/auto_emails.json - Server:
leekimerp/lee_kim_alliance_erp/doctype/auto_emails/auto_emails.py - Client:
leekimerp/lee_kim_alliance_erp/doctype/auto_emails/auto_emails.js - List client:
leekimerp/lee_kim_alliance_erp/doctype/auto_emails/auto_emails_list.js
ERPNext / standard integration
Section titled “ERPNext / standard integration”Add narrative here: which standard DocTypes (Customer, Sales Invoice, Employee, …) this document links to or replaces in workflows. See Module mapping and feature pages.
Desk & process flow
Section titled “Desk & process flow”- Typical entry: (add List / Form route or workspace name)
- Process: (add state machine / approvals / schedulers)
Fields
Section titled “Fields”| Field | Label | Type | Options | Req | RO |
|---|---|---|---|---|---|
| configuration | Configuration | Link | Auto Email Configuration | — | — |
| configuration_type | Configuration Type | Select | Application Applicant | — | Yes |
| connected_document | Connected Document | Dynamic Link | configuration_type | — | — |
| activated | Activated | Check | — | — | — |
| send_date | Send Date | Date | — | — | — |
| subtype | Subtype | Data | — | — | Yes |
| officer_id | Officer ID | Data | — | — | Yes |
| parent_document | Parent Document | Link | Application | — | — |
Structural breaks (Tab/Section/Column) are omitted from the table.