Thanks so much, that took care of it!
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kumar, Amita Sent: Tuesday, January 01, 2008 5:11 AM To: [email protected] Subject: Re: Problem with Group Notification Workflow ** Mike, There is a regular form - 'CTM:SYS-Access Permission Grps' which can be used for fetching the right group ID against the 'Assigned Group ID'. Fetch 'Permission Group ID' from the above form using the qualification - " 'Support_Group_ID' = $Assigned Group ID$ " and use 'Permission Group ID' field for sending the notification. It works. Thanks, Amita Mike Pugh Software Engineer AMERICAN SYSTEMS 13990 Parkeast Circle Chantilly, VA 20151 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. -------------------------------------------------- ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Veeral Oza Sent: Tuesday, January 01, 2008 3:02 AM To: [email protected] Subject: Re: Problem with Group Notification Workflow ** Hi, I hope this helps.... Findings: a) Group ID for CTM:Support Group and Group ID on group form are seperate entities. b) When a new Support Group is created on the CTM:Support Grroup form, a record is created in the Group Form as well. c) The Group name in the Group form contains the Group ID, which is an integer value. d) When any group notification is triggerred, the email engine looks up the Group name field of the Group form. e) The email engine does not find any match in the group form, because the group name field contains the group ID and not the group name. f) And therefore, group notifications fail. Workarounds: a) Modify the Group name on the Group Form: Instead of the Group ID, this field should be populated with the Group name. A filter can be written on the CTM:Support Group form, which modifies the Group form when any new group is created or modified. Short comings of this approach: Company1-> Org1-> Group1 and Company1->Org2->Group1 cannot exist togather. Group Name should be unique on Group form. b) If the Group Notification (sent to the Assignment Group) is to be fired from, say, HPD:HelpDesk, then create a new zTmp_GroupName field. On Submit and Modify of Assignment Group field, create a filter that reads the GroupID from CTM:SYS Access Permission form. You can query this form by specifying Company->Org->Group to get Group form's Group ID. In the Notify action, specify this zTmp field, instead of Assignment Group field. Short comings of this approach: The administrator has to be aware of such zTmp fields created for Group Notification purpose. Regards, Veeral Oza _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
<<inline: logo.gif>>
