This project has moved and is read-only. For the latest updates, please go here.


Aug 13, 2014 at 8:02 PM
At first I thought this solution would allow me to use a Email Template when I add a new Email Activity which would be a GREAT feature because the user would get to see emails before they send them. This feature is available for built-in entities but not custom entities. I don't really understand what bennefit your solution provides if I have to use it with a Workflow because I can already create dynamic emails with a regular workflow.

Am I missing something?
Aug 26, 2014 at 7:55 AM
Hi Osubrenden,

The solution gives you several features you don't have today out of the box:
  • The ability to change a template without having to change the process definition. That feature you mentioned to use an Email Template, what would happen if your template changed? You will have to go for each workflow using the same template and update its definition... painful.
  • The ability to insert dynamic fields with any number of levels in relationships (E.g. Contact => Parent Account => Primary Contact => Email Address)
  • The ability to reuse attachments from different templates, so you can save storage.
Please let know if you don't see the benefits yet or have any other question.