Mike,
The Assigned Group ID on the Incident form is not the same value as the Group ID from the Group form. It is the CTM:Support Group ID. You will need to create some workflow to get the *real* group name/id from the Group form for your assignment group. You will need to search against the 'Long Group Name' on the Group form. The 'Long Group Name' format is stored as Support Company -> Support Organization -> Support Group Name. For example, "ACME -> HR -> Payroll" would be your search string. In your workflow, you can use either the 'Group Name' or 'Group ID' value since they are the same. Cheers, Bryan From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Mike Pugh Sent: Monday, December 31, 2007 1:37 PM To: [email protected] Subject: Re: Problem with Group Notification Workflow ** George, I tried your suggestion with no luck. Now the message just appears with the Support Group ID in the Address. I also tried using the InstanceId from the CTM:Support Group form but that didn't work either. I'm going to try and dig around the Incident Management filters to see what it is passing in since that is working on our server. Thanks! Mike Pugh Software Engineer 13990 Parkeast Circle Chantilly, VA 20151 www.AmericanSystems.com <http://www.americansystems.com/> phone: (703) 968-5265 mobile: (203) 434-5082 [EMAIL PROTECTED] "Contractor of the Year - 5th Annual Greater Washington Government Contractor Awards" From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Payne, George Sent: Monday, December 31, 2007 10:11 AM To: [email protected] Subject: Re: Problem with Group Notification Workflow ** Mike, The "Send To" field is resolved in a very strict way. From the Online Manual: Note: AR System resolves the contents of the User Name field by first checking for a matching request in the User form. If found, the notification is sent to that user. If not found, the server checks for a matching request in the Group form. If the name corresponds to a group name, the notification is sent to all members of that group. If no User or Group definition is found, the contents of the User Name field are used as is and treated as a guest user of the system. This all made pretty good sense before 7.0...now the "Group Name" that it's referring to here is going to be the GROUPID (eg: 1000000089) and not the actual name as you and I would LIKE it to be. I would suggest that you try sending your email to the Assigned Group ID instead of the name. Hope that helps, Gp George Payne Corporate Applications Developer Electric Reliability Council of Texas (512) 248-3940 [EMAIL PROTECTED] ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Mike Pugh Sent: Sunday, December 30, 2007 10:17 AM To: [email protected] Subject: Problem with Group Notification Workflow I've created an escalation that should bring in a support group's name into a Notify action so that it e-mails all members of the group. For some reason it's not resolving the group name so it's not pushing the notification out to all of the group's members. I've double checked the group name several times and it's fine. Incident Management is able to send a group notification without a problem. I'm passing in $Assigned Group$ to the User Name property of the Notify action. It comes from a form I created and, for example, the form contains "Enterprise Systems" in that field, and I have an "Enterprise Systems" Support Group defined. I'm running ARS 7.1 and ITSM 7.0.02 patch 6. Does anyone have any clues? Thanks! Mike Pugh Software Engineer 13990 Parkeast Circle Chantilly, VA 20151 www.AmericanSystems.com <http://www.americansystems.com/> phone: (703) 968-5265 mobile: (203) 434-5082 [EMAIL PROTECTED] "Contractor of the Year - 5th Annual Greater Washington Government Contractor Awards" LEGAL DISCLAIMER: The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ This message is subject to and does not create or vary any contractual relationship between TuringSMI, SMI Technologies, SMI Telco, its subsidiaries or affiliates and you. Internet communications are not secure and therefore the TuringSMI Group does not accept any legal responsibility for the contents of this message. Any views or opinions expressed are those of the author. This message is intended for the addressee ('s) only and its contents and any attached files are strictly confidential. If you have received it in error, please contact the sender on the number above. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
<<image001.gif>>
