All, ConfigGuide-630.pdf Page: 287:
" Disable-Client-Operation: <tag_number_to_disable> [[<start_time>]- [<stop_time>]] [<group_ID_list>] Restricts time-consuming operations (such as reporting) during busy times, improving the overall performance. This option can be set to certain times the day. It can also exclude users of specific groups so that they are not blocked from performing the specified operation. For example, you can allow only the administrator to perform reporting during busy hours. " So ... I think the config file option is the best bet. It would allow any specified groups to be _excluded_ from the restriction. Jason's Get Entry filter option does go to one level more granular (to the user not a group) and has the added performance expense of being evaluated for every data row returned from the form. (Even for the users listed in the Run If.) I wonder if the config option will (or was) similarly expanded like the Assignee Group values were but BMC failed to document that feature? (Maybe you can be user specific in the config file? if not, then it would be a good REF idea IMHO.) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
