1

Does anyone know of a solution for User "Anthony" being able to PICK from more than ONE EMAIL ADDRESS to be the "FROM:" address when sending a Template (without using an open text box when sending the email?

This is a new requirement, as we have employees who do work for MORE THAN ONE DIVISION of our company, and they have email addresses in each Division.

Org-wide emails don't seem feasible - you'd have to create all the email addresses and then magically limit specific ones to specific people (we don't want "John at OrgONE" to email FROM: "Peter at OrgTWO").

Without actually giving them multiple SF User records (license cost, maintenance, etc), I consider the possibility of Email custom fields on their User record for each Division, but am afraid this will require Visualforce or Apex to then actually USE them.


Desired:

  • User & Primary Email:   amalena@orgONE.com
  • Division 2 Email:   amalena@orgTWO.com
  • Division 3 Email:   anthonym@theOtherORG.com

When preparing to send an email template, ideally a PICKLIST of these email addresses to populate the FROM: field.


Alternative ideas that accomplish this are welcome, or even a Plugin from AppExchange.

  • Side note: The only alternative that sounds REMOTELY possible or at least "less problematic" would be Org-Wide Emails that are GENERIC ("Sales@orgONE.com", "Sales@OrgTWO.com", etc). Not great, but maybe I'm missing how this could be the solution??? – AMM Jan 30 '17 at 16:14
  • 1
    We are doing something similar in our org and we have a validation rule on Email Message and it prevents user from selecting a from address that they are not supposed to use. Ideal solution would be to display the from addresses that they can use but I think that is not possible. – javanoob Jan 30 '17 at 16:24
  • (thanks for the one who corrected a couple typos on this) ;) – AMM Jan 30 '17 at 16:34
  • Even the thought of VALIDATION on an outgoing email is something new to me; I never would have imagined such a thing existed as I've never had this need before. That at least could be part of a solution, not the best solution, if they're typing their own "FROM" address each time, but at least (since I know their Division(s), I could lock them down to valid DOMAINS when sending). Hmm... – AMM Jan 30 '17 at 16:36
  • 1
    Sounds "logical". Biggest issue on my end is, as I investigate further, I'm really pidgeonholed into the MANAGED PACKAGE situation (Rootstock). Ugh. Will post more as I learn. – AMM Jan 30 '17 at 17:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.