LJ,
I have taken the exact same approach. (A group dedicated to client
side logging and adding/removing users from that group.) It is just so
much easier to do it that way.
The think that I think Remedy/BMC decided was something along these lines...
"
Question:
Should we support Row level access and let that help determine if
the server side logs should be sent back to the client too?
Answer:
No. It would be to much overhead. Only based the decision on the
access control lists that are "easy" to get for the user.
"
( I have not tested if a computed group could be used in as group for
this function. )
I actually think it would be great to have the ability to flag
record(s) in many forms that when any operation is done against that
record then you would get the "down stream" output of the
filter/sql/API logs from that API call forward. It think this approach
would make trouble shooting ARS workflow a LOT easier. Essentially,
you would have a kind of "log4j" dynamic scoping effect so that you
can turn logging on/off at various points in the workflow to limit the
output and focus on what is of interest. Yes this kind of thing is
much harder to develop, but it is possible. I just think the first
attempt an this feature was more "quick and dirty" than all of that.
Maybe in v7.5 we will see v2 of this feature?
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
On Wed, Feb 20, 2008 at 8:40 PM, LJ Longwing <[EMAIL PROTECTED]> wrote:
> Thank you Carey...I was beginning to think I was the only one that knew that
> you had to be EXPLICITLY listed as a member....I can't tell you how often I
> must change the server from 'Public' to something else because someone
> thinks you can set it to public and have everyone do it....if you set it to
> Public, then you need to add public to your group list to be able to client
> side filter log...I have normally created a 'Logging' group and set the
> server to that group and then added those people to that group if I want
> them to be able to log...:)
>
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
>
> [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black
> Sent: Wednesday, February 20, 2008 6:07 PM
> To: arslist@ARSLIST.ORG
>
>
> Subject: Re: Filter logging in 7.1
>
> v7.1 ...
>
> Login to the AR User tool as an Administrator.
> Navigate to the : "AR System Administration Console" ( from the "Home Page"
> Application List field) Then navigate to:
> --> System (from the Vertical Nav bar)
> --> General
> --> Server Information (Item)
>
> Then that opens the form "AR System Administration: Server Information".
>
> On the Log Files (tab) the field 'Client-Side Logging Group:' value is the
> group that the user MUST be an explicit member of.
>
> ( In versions prior to v7.1 this was in the admin tool. It is not there
> anymore.)
>
> --
> 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 www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
