L
Larry W. Virden
A number of InfoPath browser applications that I'm working on gather
information from the user and send an email off to one or more people.
The issue I have has to do with expressing the mail address within the
form.
If I hard code the address into the form, then someone, some day, is
going to have to find the form, change the address, and re-publish the
form.
That's not an ideal solution, in my mind.
One alternative that I've tried is to set up an Outlook distribution
list. That permits the form to remain the same, and allows changes to
the distribution list as needed. Of course, documentation is going to
need to exist that connects the distribution list to the applications
which use it, describing the purposes of the mail that may arrive at
the list, so that someone knows who to add or remove from the list.
The real issue is in my latest application, which has more than 2
dozen possible distribution lists.
Certainly I could ask the outlook admin to create a large series of
lists. However, I am wondering about alternatives that the community
might be using that provides at least these capabilities:
1. easy to create
2. easy to use
3. easy to make changes to the list
3. easy to specify the people who can update the list
4. easy to determine where the lists are, who is responsible for them,
and easy for the responsible person to find them
I can see a potential for using kind of SharePoint related thing -
perhaps a list or something, but I don't know how an InfoPath data
connection would get the information from the list. Also, I don't know
whether dozens of SharePoint lists don't bring with them issues of
their own.
If you have tried some alternatives and have a preference, I would
love to read about your reasons and implementation.
Thank you very much.
information from the user and send an email off to one or more people.
The issue I have has to do with expressing the mail address within the
form.
If I hard code the address into the form, then someone, some day, is
going to have to find the form, change the address, and re-publish the
form.
That's not an ideal solution, in my mind.
One alternative that I've tried is to set up an Outlook distribution
list. That permits the form to remain the same, and allows changes to
the distribution list as needed. Of course, documentation is going to
need to exist that connects the distribution list to the applications
which use it, describing the purposes of the mail that may arrive at
the list, so that someone knows who to add or remove from the list.
The real issue is in my latest application, which has more than 2
dozen possible distribution lists.
Certainly I could ask the outlook admin to create a large series of
lists. However, I am wondering about alternatives that the community
might be using that provides at least these capabilities:
1. easy to create
2. easy to use
3. easy to make changes to the list
3. easy to specify the people who can update the list
4. easy to determine where the lists are, who is responsible for them,
and easy for the responsible person to find them
I can see a potential for using kind of SharePoint related thing -
perhaps a list or something, but I don't know how an InfoPath data
connection would get the information from the list. Also, I don't know
whether dozens of SharePoint lists don't bring with them issues of
their own.
If you have tried some alternatives and have a preference, I would
love to read about your reasons and implementation.
Thank you very much.