You could add a couple of lookups to first compare the value against known users or known groups. If no user exists or if it turns out it's a group, don't send the notification (or error, or whatever)
Mark -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Frank Caruso Sent: Friday, February 29, 2008 8:56 AM To: [email protected] Subject: Group Based Email Had an issue yesterday where a user accidentally put the name of a Remedy group in a field that was supposed to contain one or email addresses. The bad part is that the user put in a group name that contained hundreds of users. I know it first checks if the value is a userid, then checks if it is a group and then checks if it is a valid email address (or something like that). 1. Is there a way to turn off the feature where Remedy attempts to decode the value being used for a notification? 2. If not, then does anyone have any tricks to avoid this from happening? Thank you Frank ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
