Brien, I would try this. (And I have not done it yet.)
A) I would add the Submitter name to one of the dynamic group fields. See if that will then also send the fields data to that username. If you can not use field 112 then add one of the 60000-60999 fields and use that field. Another possibility... B) Make a separate Notify action that only sends to the Submitter field. See if the issue is in the notification action logic with multiple recipients. (more than a "permission issue".) And just to make sure... The notification action has a 'Login Name' (that can be found in the User form) and NOT an Email address in the Notify Action 'User Name' field right? ( Sending a notification to an email address requires Public on the fields. However, sending a notification to a defined User can use the Users access controls. However, sending a Notification to multiple groups/Users has a restriction to the least common denominator.) v6.3 EmailEngine-630.pdf pg: 72 " An email sent to more than one user will only contain data that only the user with the most restricted permissions can view in Remedy User. For example, if an email is sent to both an administrator with full access permissions and to a user with only Public access, only data allowed by Public access will be included in the email. " And as one (hopefully) final idea... C) Try sending the email to the Submitter during a Modify event. Does that resolve the issue? ( Just another WAG, but it might be that the ARS server does not recognize the 'Login Name' as the 'Submitter' during the submit process because the value can still be changed during Submit Filters.) Hope some part of that helps. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On Wed, Jul 2, 2008 at 2:27 PM, Brien Dieterle <[EMAIL PROTECTED]> wrote: > ** I'm considering filing a bug report: > > Steps to reproduce: > Create two users, User1 and User2 > Create a Form w/ public access and add Field 112 (assignee Group). > Remove Public access to all fields (but not the form) and add Read-only > access for Submitter and Assignee Group to all fields. > Allow any user to submit to all fields on the form. > Create a filter for this form with action: Submit, with two notify tasks. > The first notify goes to $Submitter$, Include all fields. The second notify > goes to User2, Include all fields. > > Submit a request to the form with User1 in the Submitter field, and type in > 'User2' (with single quotes) in the Assignee Group field. > > Expected result: > User1 ($Submitter$) does not get any fields in the email. > User2 gets all fields in the email > > Desired result: > User1 ($Submitter$) gets all fields in the email. > User2 gets all fields in the email > > > The Email Guide states that you can send the following types on information > in a notification: > > "Contents of selected fields (if the user being notified has the appropriate > permission for those fields)" > > At the very least the documentation is not correct, since User1 definitely > has appropriate permissions :-) > > Thanks for any ideas! > > Brien <snip> >>> From: Action Request System discussion list(ARSList) >>> [mailto:[EMAIL PROTECTED] On Behalf Of Brien Dieterle >>> Sent: Wednesday, July 02, 2008 12:29 PM >>> To: arslist@ARSLIST.ORG >>> Subject: Re: submitter access to fields in notify >>> >>> >>> >>> ** Oops-- >>> AR Server 7.1 Patch 003 >>> Windows 2003 >>> SQL Server 2005 >>> >>> On Wed, Jul 2, 2008 at 9:26 AM, Brien Dieterle >>> <[EMAIL PROTECTED]> wrote: >>> >>> Hi List! >>> >>> I am having a really weird problem. I have a form that has NO Public >>> access to any fields. All permissions are granted by Submitter, a static >>> group, or Assignee Group. All of these groups have read permissions to all >>> of the fields on this form. >>> >>> I have a filter that sends three notifications, one to each of these >>> groups. The Static Group and Assignee Group work just fine. I can select >>> fields (Include Fields) or add an HTML template and include field variables >>> in there, and they are displayed. Perfect. >>> >>> However, the Submitter cannot see fields that have been selected (Include >>> Fields), and if I add an HTML template, those fields are blank there as >>> well. However, the Submitter can see fields that I have added to the >>> "Subject Line:" or the "Notify Text" (If I don't use a template). In this >>> way I can include all the fields in the email, but I cannot 1) use a >>> template, nor 2) use the Include Fields: dialog. >>> >>> Naturally, the Submitter can view the Record just fine using the User >>> tool or Midtier. >>> >>> So any help figuring out this puzzle would be much appreciated! >>> >>> Brien _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
