Assuming that works, what an elegant and simple solution!
Doug -- Doug Blair Sent from my iPhone4, typographic errors likely +1-224-558-5462 On Jun 8, 2011, at 6:16 PM, Juan Ingles <juan.n...@gmail.com> wrote: > An easy way to prevent this is to create a user record with the login "0" > Then "0" will resolve to that user's email address instead of the public > group. > > As other people have pointed out, there are lots of ways for "0" to > end up in the to address. > > Juan Ingles > > > > On Wed, Jun 8, 2011 at 6:49 AM, Andrew C Goodall <ago...@jcpenney.com> wrote: >> ** >> >> All, >> >> >> >> FYI – for ITSM users >> >> >> >> We had an issue last week in which a service desk associate created a >> proposed people record for a vendor and entered a zero as the persons email >> address. >> >> Upon creating the incident with the new person as the customer the BMC >> workflow treated “zero” in the email field as meaning I need to email >> EVERYBODY that has a people record!!!! For use that is over 300,000 records! >> >> >> >> Needless to say our executives were not very happy about this, we had opened >> a CRITCAL issue with BMC on this because it was not as simple as deleting >> all the relevant records from “AR System Email Messages” form since the NTE >> functionality was shipping 100 records or so every few minutes to be >> processed by the email engine in “AR System Email Messages”. >> >> >> >> We needed to STOP the messages from getting processed by NTE, but BMC >> support did not have a remedy (HA – pardon the pun), they said we just had >> to let them process – RIDICULUOUS! Furthermore we found out through this >> issue that this is an “AS DESIGNED” feature – RIDICULULOUS! >> >> >> >> So be warned if you don’t want your service desk to accidently email >> everyone in the company add an active link to validate the value in the >> email field when creating a people record. >> >> >> >> It is breath taking to me why BMC would think this is a good “AS DESIGNED” >> feature. I can understand needing that capability for use in workflow – but >> for goodness sake only allow it on a back end hidden field e.g. a z_ field, >> and NOT a forward facing field editable by users. >> >> >> >> Regards, >> >> >> >> Andrew Goodall >> >> Software Engineer 2 | Development Services | jcpenney . www.jcp.com >> >> >> >> The information transmitted is intended only for the person or entity to >> which it is addressed and >> may contain confidential and/or privileged material. If the reader of this >> message is not the intended >> recipient, you are hereby notified that your access is unauthorized, and any >> review, dissemination, >> distribution or copying of this message including any attachments is >> strictly prohibited. If you are not >> the intended recipient, please contact the sender and delete the material >> from any computer. >> >> _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
