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=eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiaHR0cHM6Ly9kemY4dnF2MjRlcWhnLmNsb3VkZnJvbnQubmV0L3VzZXJmaWxlcy8yMzgxLzM3MTcvY2tmaW5kZXIvaW1hZ2VzL3F1LzIwMjUvaW1hZ2UoNykucG5nIiwiQ29uZGl0aW9uIjp7IkRhdGVMZXNzVGhhbiI6eyJBV1M6RXBvY2hUaW1lIjoxNzgwMTY1NDQ5fX19XX0_&Signature=BmpfGBVreXsI4mct0g~YwW8p8z~Hchpwe3sFEASfOJ-49NOK9RkY1lb5hV13bFRp2ftcZwzvp-pzNu1TAqkGtdlNCe7TQVNB-ktVK~8oTEDCl7gO3neWi19AHzXsXX4gplGINIll4e8UwGeG-f5jMfkqjzR8lcuidomIMNT-s~fEnIgJMsxKCzwB6p-UlZM0OBbGdM3Qi7raTw8YXQYUP5GEYxSNerUIQ1956WFK3hfLQhoTAi2BhVL9YM0TZaM28BghwY8TYjkwrzLzs~xLryPpgz-hpMTxf-Q0SDiOpjrhE5IytX6D8deFOJmA8lTV29pI2ZsWAKDv9AsyhRXYFg__&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=eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiaHR0cHM6Ly9kemY4dnF2MjRlcWhnLmNsb3VkZnJvbnQubmV0L3VzZXJmaWxlcy8yMzgxLzM3MTcvY2tmaW5kZXIvaW1hZ2VzL3F1LzIwMjUvaW1hZ2UoNikucG5nIiwiQ29uZGl0aW9uIjp7IkRhdGVMZXNzVGhhbiI6eyJBV1M6RXBvY2hUaW1lIjoxNzgwMTY1NDQ5fX19XX0_&Signature=NRZ~iAuj6UcsqDWgwPxM6amiK2Log~Wx4-6VUDs0SC5qLnWj3C2Y-3EVgg9~bTiXpgHpT57qkhEpw8U2tKLMX5Eqb8b1by4WX~eBCTock1tPXRFfd2LmJcpyUZEnUzWB4I4cXW3fW4InFZrsPa1mCjLHviqTogtwV0s3ZmoWfnsZICHt4a5vfVljm0rkM368Z2HUc2Q7OItyUPWcxY~ekhA9BOKcVbDt3aQjS6hIJbqyX7n6c6yOpKgsNMCrE9Ca4X9DEZocfoFDDEtbsjJHuAEmpENa~5Wum1An~GBQLy6bTMizvfM-2-9b1KwHAs8xZvCQSapv7LZQRnPjcR4ZzQ__&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.