Neel, I see your message. Bruce -----Original Message----- From: Action Request System discussion list(ARSList) on behalf of SUBSCRIBE arslist Neel Sent: Wed 4/18/2007 10:21 AM To: arslist@ARSLIST.ORG Cc: Subject: pleae respond till RESOLVED
Hello ARslisters, I am new to ARSlist and I am not sure if my messages are going through. If you guys can see this email, could you please respond to it? I'm a bit confused here and need to make sure my messages are reaching you actually. Thank you, Neel Gautam -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Axton Sent: Wednesday, April 18, 2007 11:47 AM To: arslist@ARSLIST.ORG Subject: Re: ARS7 & Matching Assignee Group field Computed groups are automatically assigned to users based on the user's regular group membership. You just define the qualification that determines whether a user is in a computed group or not and the server takes care of the rest. Read up on computed groups; I think they fit the bill. If you want to manage row-level locking based on a condition of a number of other groups for which a user is a member, you are going to have to maintain the data to drive that somewhere. It's the price you're going to have to pay for your requirement. Axton Grams On 4/18/07, Andrew Hicox <[EMAIL PROTECTED]> wrote: > I'm sorry, I should have clarified. > Computed groups would work, except that I'm going to have (literally) > hundreds of base groups, any combination of which might end up being in > the 'Assignee Group' field together. > > Unless there's a way to construct computed groups on the fly, I think > I'd need to create thousands of computed groups manually to cover every > possible combination of the base groups. > > Uhm ... is there a way to create computed groups on the fly (and assign > them to specific users on the fly as well)? That might work, though > strikes me as overly complicated. > > thanks again, > > -Andrew > > On Apr 18, 2007, at 11:08 AM, Axton wrote: > > > Computed Groups could help you with this? > > > > Create a computed group to your qual "GroupA and GroupB..." > > > > Put the computed group in the assignee group field. > > > > Haven't done this first-hand, so I'm not sure if you will run into > > issues; but theoretically it should work. > > > > Axton > > > > On 4/18/07, Andrew Hicox <[EMAIL PROTECTED]> wrote: > >> Hello everyone: > >> > >> In ARS7 you can use the 'Assignee Group' (field id 112) field to > >> control access to records (row-level locking). If you grant the > >> 'Assignee Group' permission on the 'entry id' field, then only users > >> who are in the group specified in the 'Assignee Group' field are > >> granted permission to view the record. > >> > >> This works just fine for me. However, I need to make this work with > >> multiple groups. > >> Specifically, the requirement is that a user must be in ALL of the > >> groups listed in the 'Assignee Group' field, to have access to the > >> ticket. > >> > >> So for instance if 'Assignee Group' = "Group1 Group2 Group3", a user > >> must be in all three groups to view the ticket (instead of just one of > >> the three, which is apparently the default multiple group behavior). > >> > >> Strangely enough, I can "trick" ARS into doing this with the following > >> one-off procedure ... > >> > >> 1) check 'Enable Multiple Assign Groups' in "Server Information" > >> dialogue, click "Apply" > >> 2) create a ticket with multiple groups in the 'Assignee Group' field > >> 3) uncheck 'Enable Multiple Assign Groups' > >> > >> Under those circumstances, ARS7 will behave exactly the way I want it > >> to. That is, a user must be in ALL of the groups in the 'Assignee > >> Group' field to view the ticket. > >> > >> However, I can't make any new tickets like this while it's in the > >> "AND" > >> matching mode (instead of "OR"). ARS7 gives me an error if I try to > >> create tickets with multiple groups in the 'Assignee Group' field, > >> unless the 'Enable Multiple Assign Groups' is enabled. > >> > >> If 'Enable Multiple Assign Groups' is enabled, ARS7 uses "OR" to match > >> the 'Assignee Group' field (user can be in any one of the groups). > >> > >> ARS7 will only use "AND" to match the 'Assignee Group' field (user has > >> to be in ALL groups) if 'Enable Multiple Assign Groups' is turned off. > >> > >> How can I just tell ARS7 to use "AND" to match the multiple assignee > >> groups instead of OR (as it does when the feature is turned off?) > >> > >> PLEASE HELP! > >> I'm pulling my hair out on this one! > >> > >> Thanks, > >> > >> -Andrew > >> > >> ______________________________________________________________________ > >> _________ > >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > >> ARSlist:"Where the Answers Are" > >> > > > > _______________________________________________________________________ > > ________ > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > > ARSlist:"Where the Answers Are" > > > > > Andrew N. Hicox > Hicox Information Systems LLC > Manassas, VA USA > http://hicox.com <http://hicox.com/> > [EMAIL PROTECTED] > 703-367-9085 > > ________________________________________________________________________ _______ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" > ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" ##################################################################################### The information contained in this electronic mail message, including attachments, if any, is PetSmart confidential information. It is intended only for the use of the person(s) named above. If the reader of this message is not the intended recipient, or has received this message in error, you are hereby notified that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you are not the intended recipient or have received this message in error, please notify the sender via e-mail and promptly delete the original message. #####################################################################################