In case anyone is interested, I opened a ticket with BMC and the tech was able to reproduce it on his end, and agreed it didn't seem to be working as designed and sounded like a defect. Waiting to hear back if they confirm it is a defect or not...
So, does everyone here basically have Public permissions added to everything, if they want to use email? Brien On Wed, Jul 2, 2008 at 2:27 PM, Brien Dieterle < [EMAIL PROTECTED]> wrote: > I tested A) by adding User1 to Field 112 and then sending the notification > to $Submitter$. Since $Submitter$ is in field 112, the included fields * > are* in the email. I also created a new Dynamic Group 60988 and added > User1 to this field. This also corrected the problem. > > I tested C) by adding the "Modify" action to the filter, and modified the > record with an administrator account. The same two emails are resent, with > User1 not having the fields, and User2 having fields (User1=Submitter and > User2=Field112). > > So-- it looks like the Notify action is simply broken for the core fields: > Submitter *and *Assignee (I just tested this all with the Assignee field > as well). To summarize: Submitter and Assignee permissions are broken > during the Notify action, specifically for Included fields and Template > fields (and specifically *not* Subject line: $fields$ and Notify Text: > $fields$). Assignee Group and other Dynamic group permissions are NOT > broken and work as the documentation suggests. > > Brien > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
