Filters always run with admin privelages. Be careful creating computed groups on the fly, as each time you create or update one, the entire user form dataset gets scanned/updated.
Create a computed group manually and watch the cpu on your arserver and db server. Also keep in mind that cacheing (group) operations will occupy the admin thread until they complete, blocking any other admin operations. Axton Grams On 4/20/07, Andrew Hicox <[EMAIL PROTECTED]> wrote:
Hello all: I'm still working on my issue regarding the assignee group field. I think I've worked out a system where I can create computed groups on the fly as tickets are submitted for various combinations of the regular groups (which are synced from the external database). I'd like to spawn these computed groups with a filter that executes on a ticket submission or modify. However, I believe one would need Admin privileges to submit new group fields, and I'm fairly certain that filters that fire on submit or modify operations execute with the permissions of the user who triggered them. Obviously all of my users can't be Admins. Is there a way to specify a filter to always run as admin? my other option seems to be setting up flags in the tickets so that they're picked up by escalations which would do the dirty work as the admin user. so ... is there something like that? am I completely wrong about filters firing with user permissions? if I'm right about that, is there a way to escalate privs for just one filter ? thanks, -Andrew Andrew N. Hicox Hicox Information Systems LLC Manassas, VA USA 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"
