Aug 2nd, 2011, 8:56 PM
Hey Mark,
I do wish we had talked sooner, however I still don't think the feature makes sense as it was - or maybe I'm just not understanding something.
Let me try to explain why it doesn't make sense to me.
Here's a scenario. Imagine an email template that's sent to these people:
- the person who submitted the form
- client #1 (cc)
- client #2 (cc)
Since this is a single email template, the content of the email will be the same, as it's sent to all of them at the same time. So in this scenario, if the email content included a user placeholder, what values would actually end up in the email? Values from client #1 or #2?
Neither really makes sense.
The ONLY circumstance in which those user placeholders would have made sense would have been if the email template contained only a single client account (either as the main recipient, cc, bcc, "from" or "reply-to"). In that case, I could get the code to figure out what values to use. But, in that scenario, the placeholders would become redundant: the person constructing the email template would have known who'd be the client that was relevant to the email template (since they'd have just specified them) and they could just enter in the information manually. [True, the placeholders would have had the benefit of being automatically updated as their account updated, but I still think it would raise confusion about when those placeholders could be used and when not.]
See what I mean?
Let's get to the bottom of this. This is one of the very few times I've dropped functionality, and I hate to do it.
- Ben
I do wish we had talked sooner, however I still don't think the feature makes sense as it was - or maybe I'm just not understanding something.
Let me try to explain why it doesn't make sense to me.
Here's a scenario. Imagine an email template that's sent to these people:
- the person who submitted the form
- client #1 (cc)
- client #2 (cc)
Since this is a single email template, the content of the email will be the same, as it's sent to all of them at the same time. So in this scenario, if the email content included a user placeholder, what values would actually end up in the email? Values from client #1 or #2?
Neither really makes sense.
The ONLY circumstance in which those user placeholders would have made sense would have been if the email template contained only a single client account (either as the main recipient, cc, bcc, "from" or "reply-to"). In that case, I could get the code to figure out what values to use. But, in that scenario, the placeholders would become redundant: the person constructing the email template would have known who'd be the client that was relevant to the email template (since they'd have just specified them) and they could just enter in the information manually. [True, the placeholders would have had the benefit of being automatically updated as their account updated, but I still think it would raise confusion about when those placeholders could be used and when not.]
See what I mean?
Let's get to the bottom of this. This is one of the very few times I've dropped functionality, and I hate to do it.
- Ben