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 On Wed, Jul 2, 2008 at 10:13 AM, Brien Dieterle < [EMAIL PROTECTED]> wrote: > I've read that on this list as well but I'm not sure if that is entirely > true (anymore?). The Include fields work perfectly for the dynamic group: > Assignee Group, as well as a Static Group. There are No Public permissions > at all on this form. It is only the dynamic group: Submitter that has the > strange problem. And even then it is only for Include and Template fields > and does not affect Subject: or Notify Text. > > Brien > > > On Wed, Jul 2, 2008 at 9:55 AM, Tanner, Doug <[EMAIL PROTECTED]> > wrote: > >> ** >> >> From Past experiences - I have found that you MUST include Public >> Permissions on the fields in order to Include within the Notify Action >> >> (You can of course hide them on the form with Workflow, but at the >> database level you need Public- View) >> >> Doug >> >> >> ------------------------------ >> >> *From:* Action Request System discussion list(ARSList) [mailto: >> [EMAIL PROTECTED] *On Behalf Of *Brien Dieterle >> *Sent:* Wednesday, July 02, 2008 12:29 PM >> *To:* [email protected] >> *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 >> >> >> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" >> html___ >> DISCLAIMER Important! This message is intended for the above named >> person(s) only and is CONFIDENTIAL AND PROPRIETARY. If you are not the >> intended recipient of this e-mail and have received it in error, please >> immediately notify the sender by return email and then delete it from your >> mailbox. This message may be protected by the attorney-client privilege >> and/or work product doctrine. Accessing, copying, disseminating or re-using >> any of the information contained in this e-mail by anyone other than the >> intended recipient is strictly prohibited. Finally, you should check this >> email and any attachments for the presence of viruses, as the sender accepts >> no liability for any damage caused by any virus transmitted by this email. >> Thank you. >> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" >> html___ > > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
