|
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. Thanks, Terry Anderson >What's the concept? >1 - You change the customer record. email >Accounting_Manager@xxxxxxxxxxxxxxxxxx? >2 - You change the customer record. Email JoeBlow@xxxxxxxxxxxx? >3 - ?????? > >1 = Very static. Heck, that could be hardcoded. And your exchange >server >would know who to route it to. Personally my one Domino record has 5 >email addresses. >2 = Customer contact file. Should already be a database on your >iSeries >for this anyway. Just add an email address if it doesn't already >have >one. > >We also have an email system on our i5 that uses a few parameter to >email >out to various people. For example, there's a VARYON group. When we >run >our program that's ancillary to QSTRUP it emails certain people. >That >group is but one part of the key. > >Rob Berendt
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.