Difference between revisions of "HowTo:Send Messages to Multiple Recipients"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 15: | Line 15: | ||
===Record-Controlled=== | ===Record-Controlled=== | ||
: An [[Email | : An [[Email Address field]] can be added to the object. For a given record, that field can contain a single email address or a comma-separated list of addresses. That email field is then used as a template variable in one of the template lists. | ||
:'''Advantage:''' Every record can have it's own unique set of addresses | :'''Advantage:''' Every record can have it's own unique set of addresses | ||
:'''Disadvantage:''' Address values have to be added to every record. | :'''Disadvantage:''' Address values have to be added to every record. | ||
| Line 25: | Line 25: | ||
===Using a "Configuration Object"=== | ===Using a "Configuration Object"=== | ||
::* An [[Email | ::* An [[Email Address field]] can be added to a ''configuration object''. That field can contain a single email address or a comma-separated list of addresses. | ||
::* That Email Field could also contain the | ::* That Email Field could also contain the | ||
:'''Advantage:''' xx | :'''Advantage:''' xx | ||
Revision as of 02:16, 29 January 2014
|
For: Designers See more: |
There are many ways to send a single message to multiple recipients. This writeup summarizes the possibilities, so you can choose the mechanism that is most appropriate for your application.
User-Controlled
- When sending an email from a Case or from any other record in the system, a user can add as many recipients as they like.
- Advantage: Infinite flexibility
- Disadvantage: Requires manual effort that becomes excessive when duplicated my different users and/or repeated by the same user.
- Learn more: Respond to a Case or Add a Note
Template-Controlled
- When creating an Email Template, a comma-separated list of recipients can be specified.
- There are multiple ways to do it:
- Individual recipient addresses can be hard-coded into the To, Cc, or Bcc fields.
- Template Variables can be used include individual email addresses from related Contacts and Users, by referencing Lookup fields contained in the current record.
Record-Controlled
- An Email Address field can be added to the object. For a given record, that field can contain a single email address or a comma-separated list of addresses. That email field is then used as a template variable in one of the template lists.
- Advantage: Every record can have it's own unique set of addresses
- Disadvantage: Address values have to be added to every record.
Using an External "Alias"
- One or more of the addresses contained in an email field could also be an email alias--a list of email addresses maintained on a separate server.
- Advantage: Every record can have it's own unique
- Disadvantage: xx
Using a "Configuration Object"
- An Email Address field can be added to a configuration object. That field can contain a single email address or a comma-separated list of addresses.
- That Email Field could also contain the
- Advantage: xx
- Disadvantage: xx
Mechanism
- Description.
- Advantage: xx
- Disadvantage: xx
Wrap Up
...What you've done.... ...List of things you've explored/learned about/played with:
- ...
- Learn more:
- ...