Open Nicholas-Westby opened 8 years ago
+1
Our particular use case has a standard contact form that is emailed to different people depending on the location in the site. I was initially hoping to set this up as one form, two layouts (English and Welsh) and many configurations (one for each combination of layout and email handler). Having to pick handlers per form necessitates a whole new form for each. This problem is compounded by the lack of a copy form feature.
We're also looking to add email recipients on a per-page level under Umbraco > Content nodes. Usual requirements for our clients is to specify a default To: recipient email address in the root node, then allow an override email address per page.
Populating a variable on the Page Template from a CMS field seems like it could be a simple way to facilitate this, with Formulate "watching" for this value and utilising it when present. ie, var formulateToEmail = @Umbraco.Field("formulateToEmail") or some such.
Of course, this rather basic idea would not play nicely when two forms are present on one page (which is common for us too). But maybe there's a clue in this approach that someone, more tech savvy than I, could build upon.
It would also be nice to be able to specify CC and BCC Recipient Emails. BCC is often used to send all form submissions to a catch-all inbox which can be used as a complete activity history and for auditing.
Hi @FuelAgency,
I have a solution for this, but I'd prefer to keep the discussion for this issue focused on the primary issue. If you post a message over in the forum, I would be happy to give you some ideas: https://our.umbraco.org/projects/backoffice-extensions/formulate/formulate-questions/
I have done similar myself and it's relatively straightforward once you know how to go about it.
Regarding BCC vs CC vs TO, that is currently not built-in, so it would be well suited for a feature request. IIRC, Formulate currently uses BCC exclusively.
For example, it is common to want to send emails to different people based on which page a form appears on. Would be much easier to facilitate this if handlers had their own tree section and could be picked as part of the form configuration.