How to configure (via Custom Metadata: e2a Customer Settings)
Step 1 — Create a new custom Metadata Type e2a Customer Settings (skip this step if it already exists in your org)
- Go to 'Setup' and type 'Custom Metadata Type' in the quick find box.
- From the results, open 'Custom Metadata Type'.
- Press on 'New Custom Metadata Type' to create a new Custom Metadata Types.
- Set the Label as: e2a Customer Settings
- Set the Object Name as: e2a_Customer_Settings__mdt (note the "__mdt" gets added automatically)
- Set the Description as: This Custom Metadata type holds records related to different settings for e2a.
Step 2 — Create the Value field on e2a Customer Settings (only if it doesn’t exist)
-
Go to Setup → Custom Metadata Types.
-
Open e2a Customer Settings → Fields & Relationships → New.
-
Create the field:
-
Field Label:
Value -
API Name:
Value__c -
Data Type: Text
-
Length:
255
-
-
Save.
If your org already shows Value (Value__c, Text 255) on this type, skip Step 1.
Step 2 — Create the desired setting record(s)
-
Setup → Custom Metadata Types → e2a Customer Settings → Manage Records → New.
Record A — Owner/assignee notifications
-
Label:
Dmo_EH_Trigger_User_Email -
Name (Developer Name):
Dmo_EH_Trigger_User_Email -
Value (Value__c):
trueorfalse-
true→ send assignment/owner emails -
false→ suppress assignment/owner emails
.png?Policy=eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiaHR0cHM6Ly9kemY4dnF2MjRlcWhnLmNsb3VkZnJvbnQubmV0L3VzZXJmaWxlcy8yMzgxLzM3MTcvY2tmaW5kZXIvaW1hZ2VzL3F1LzIwMjUvaW1hZ2UoNykucG5nIiwiQ29uZGl0aW9uIjp7IkRhdGVMZXNzVGhhbiI6eyJBV1M6RXBvY2hUaW1lIjoxNzczNDE3MjI3fX19XX0_&Signature=k0PToNcdeWVOkG83tu~A0lCKS0gQEw9F4gpvYkltOzpgvTEb~bpKof0OoUBPdp5Xq5MA~JLvaAJBOi0VTKeAPIJ7g6hz~Ip1jbYTRqJt9nvly6mwtu~cv-9TxVm6IZgq-PEGIo7odNSnl50t1VLzsBj5U~7wzW6FOgIx7w4bIBIosJMYpANXHFfto2smJD5OsaOmKA-KWOt-sywfjaV18Q9-J~URp7VVoxjWPCEQwi2CvIdBakoPOeF0GXK3Jn2f-hTHI9whHYkrYoitHN3Oa3ibLpNJT6MbGJ-CAyB9c66FEXhlwudQ3j-VNCopwS8Bw~Wn4gezV0Gsrg7duwcoAw__&Key-Pair-Id=K2TK3EG287XSFC)
-
Record B — Auto-response emails
-
Label:
Dmo_EH_Trigger_Auto_Response_Email -
Name (Developer Name):
Dmo_EH_Trigger_Auto_Response_Email -
Value (Value__c):
trueorfalse-
true→ send auto-responses (from Auto-Response Rules) -
false→ suppress auto-responses.png?Policy=eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiaHR0cHM6Ly9kemY4dnF2MjRlcWhnLmNsb3VkZnJvbnQubmV0L3VzZXJmaWxlcy8yMzgxLzM3MTcvY2tmaW5kZXIvaW1hZ2VzL3F1LzIwMjUvaW1hZ2UoNikucG5nIiwiQ29uZGl0aW9uIjp7IkRhdGVMZXNzVGhhbiI6eyJBV1M6RXBvY2hUaW1lIjoxNzczNDE3MjI3fX19XX0_&Signature=qR~0Un1Qw0mlrBl87RrxCjaYYpSpb71bFRpPZUXXVT5iL3C9tKDOCGi3VQs-0TcFcM2U-IfujnegP~tdeZyIU8W3hjKvIgJ9JIuNZgbdZP3~csjMQC779yvWGTDaAqAfYRPAkC-1lIYIbP65gtd1oBOhbVgFnLgjdxCbuCh26JFTZnm~bMcWL-Vh8n-NR27UbB1taZGy2UZCbSAgGDQ~qjQwVpSjnLO5iAmwjJ8PJ0adNSRgQlv3SdrY2z8M4SkFneH9s2SKH9~AHFa27FsqOVPYJeuUfsC~ywoRtHfHR6lo0pwa5Hg5BFQFXSFvkVzIqsnCG~DcLCCQflh5pB7fqg__&Key-Pair-Id=K2TK3EG287XSFC)
-
Notes
- Enter
true/falsein lowercase (no spaces). - If a record is missing, e2a treats the setting as true (emails ON) by default.
Quick outcomes guide:
- Dmo_EH_Trigger_User_Email =
true, Dmo_EH_Trigger_Auto_Response_Email=true→ both emails sent - Dmo_EH_Trigger_User_Email =
false, Dmo_EH_Trigger_Auto_Response_Email=true→ no assignment email; auto-response sent - Dmo_EH_Trigger_User_Email =
true, Dmo_EH_Trigger_Auto_Response_Email=false→ assignment email sent; no auto-response - Dmo_EH_Trigger_User_Email =
false, Dmo_EH_Trigger_Auto_Response_Email=false→ no system emails
You now have simple, on/off control of Salesforce’s assignment and auto-response emails generated during e2a inbound processing—so your notifications match your process, not the other way around.
Please contact us at support@ortooapps.com for any questions.