|
On 2/6/06, as400tech@xxxxxxxxxxx <as400tech@xxxxxxxxxxx> wrote: > Rob, > I guess I need to clarify what is happening. The changes are not going > back to the customer. They are going to the plants that make the > products. There is no separate customer contact file. The customer > contact is included in the customer master file. Because we use a third > party package, we can not change the customer master file. > > Not all plants service all customers. So, if corporate changes > something on customer number 123 then an email would need to be sent to > Bill@plant1, Bob@plant1, Sally@plant5, bubba@plant11 and Jim@plant15. > A change to customer number 456 could mean that an email would need to > be sent only to Bill@plant1 and Bob@plant1. The corporate user will be > the one to know what plant makes what product for which customer. I > figured that if I could get Outlook to open a blank email, then the > corporate user could enter what information about the customer was > added, changed, or deleted and send it out to the correct plant. This strikes me as a solution that will quickly stop being used, given that pressing ESC will cancel the email message. And what happens if that person doesn't notify the correct people, or changes the subject line by mistake? Far better to use the built-in emailing capabilities of the system, the configuration of which has been discussed to death on these lists. An easy solution is to have your mail guy create a list on the mail server (perhaps material_managers@xxxxxxx) to which your trigger program sends these notifications. You might also create generic system directory entries with the relevant email addresses. If the plant folks have a small issue with erroneous emails, remind them of the delete key. If they have a huge problem with getting emails not relevant to their plant, then you can figure out a way to determine the plants to notify from the customer info. I am sure the folks on the list would have lots of ideas here. Good luck.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.