In BMC's SRM class, they let you know that you'll have to "fine tune" the notifications to your environment. For us that meant turning off filters that generate notifications to requesters from the back office applications. Essentially we let the SRM notifications provide all communication with the end user.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Jim Coryat Sent: Friday, April 24, 2009 9:44 AM To: [email protected] Subject: Remedy, ITSM and SRM Notifications, major spammage This is a multi-part message in MIME format. ------_=_NextPart_001_01C9C4FB.E3B94690 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable We have recently implemented the ITSM applications as well as the Service Request Management module. What we are seeing is a number of email notifications that are sent to customers, some are completely unnecessary. In going into the NTE:CFG-Notification Events and try and turn some of the notifications off, they still show up. Does anyone have any experience in this area and could spare a few pointers in cleaning this up? Right now the users are starting to blindly delete the BMC Remedy notifications since they are getting spammed with these continuously. =20 Thank you for any advice you can provide. =20 Jim Coryat _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are" ------_=_NextPart_001_01C9C4FB.E3B94690 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable ** <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:x=3D"urn:schemas-microsoft-com:office:excel" = xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" = xmlns:a=3D"urn:schemas-microsoft-com:office:access" = xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" = xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" = xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" = xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" = xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" = xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" = xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" = xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" = xmlns:html=3D"http://www.w3.org/TR/REC-html40"; = xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/"; xmlns:D=3D"DAV:" = xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/"; = xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml"; = xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/"; = xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/"; = xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#"; = xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp"; = xmlns:udc=3D"http://schemas.microsoft.com/data/udc"; = xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema"; = xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"= xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"; = xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/"; = xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/"; = xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"; = xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap"; = xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile"; = xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart"; = xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/"; = xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup"; = xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig"; = xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig= nature" = xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006= " xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"; = xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi= ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages"; = xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"= = xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag= es" = xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/= " = xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub= lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" = xmlns:st=3D"" xmlns=3D"http://www.w3.org/TR/REC-html40";> <head> <meta http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)"> <style> <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri","sans-serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri","sans-serif"; color:windowtext;} .MsoChpDefault {mso-style-type:export-only;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.Section1 {page:Section1;} --> </style> <!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3DEN-US link=3Dblue vlink=3Dpurple> <div class=3DSection1> <p class=3DMsoNormal>We have recently implemented the ITSM applications = as well as the Service Request Management module. What we are seeing is a = number of email notifications that are sent to customers, some are completely = unnecessary. In going into the NTE:CFG-Notification Events and try and turn some of = the notifications off, they still show up. Does anyone have any = experience in this area and could spare a few pointers in cleaning this = up? Right now the users are starting to blindly delete the BMC Remedy = notifications since they are getting spammed with these continuously.<o:p></o:p></p> <p class=3DMsoNormal><o:p> </o:p></p> <p class=3DMsoNormal>Thank you for any advice you can = provide.<o:p></o:p></p> <p class=3DMsoNormal><o:p> </o:p></p> <p class=3DMsoNormal><span = style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Jim Coryat</span><o:p></o:p></p> </div> </body> </html> _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ ------_=_NextPart_001_01C9C4FB.E3B94690-- _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
