Hello Listers, ARS 6.3 Patch 21 SQL Server 2000 Windows 200 server
I am reworking a small help desk application and I was wondering if there is a general philosophy for handling email lists. We are identifying a list of people "types": Management Field Rep Ticket Expediter Warranty Clerk etc. There will be a few people in each type and the names can change frequently. More that once a month. And a person can be multiple types. ( Field Rep AND Warranty Clerk). We wouldn't want them getting two emails if both types were selected for notification. Usually I make a group and use it to send the notifications but I was concerned that adding a new "type" and the constant flexibility of the user community among the types would be better suited to a data driven form. I like the use of a Group in the email notification for expanding the addresses. I'm not sure if I have to worry about the To: field and a 255 character limit if I use a non-standard Notification workflow. Would dynamic or computed groups be a solution? My ultimate goal is to hand over the list maintenance to a power user. Thanks in Advance, John J. Reiser Software Development Analyst Remedy Administrator/Developer Lockheed Martin - MS2 The star that burns twice as bright burns half as long. Pay close attention and be illuminated by its brilliance. - paraphrased by me _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
