Mike, It might have worked that way before. ( I honestly do not remember.)
However I think if you are using "Public" and actually put that in your group list then I think you will find that it works too. ( You just can not depend on the implicit "membership" for the group that is listed.) However, our decision was to create a special group (not Public, or Administrator) so that we could add it to users and then take it away without affecting their other permissions. :) Sure you have to add that group to your Administrator users, but that is a small set. And you can make 'Group List' changes during the day without any real fuss. -- 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 2/15/07, Mike Parker <[EMAIL PROTECTED]> wrote:
Hi Carey: You were indeed correct - I had to flip the Client Side Logging to "Administrator". To be honest however, I don't ever remember having to do use explicit groups however to enable this feature in prior versions (unless I just never noticed). Since I originally had it set to "Public", and all users that can log into Remedy are technically in the "Public" group, I would think that this should allow them to perform filter logging. ...Unless it never worked this way in the first place (and I guess I was just really lucky because it always worked for me in the past) =$ >From: Carey Matthew Black <[EMAIL PROTECTED]> >Reply-To: [email protected] >To: [email protected] >Subject: Re: User Tool - Client Logging >Date: Wed, 14 Feb 2007 22:56:41 -0500 > >Mike, > >The Server setting that identify the group that is allowed to do >client side logs MUST be in the users Group List explicitly. ( I have >found that even Administrator does not automatically get you access to >that feature.) > >I have also noticed some strangeness if your User Tool is connected to >multiple ARS servers and you are part of the *special* group on one of >the servers but not on all of them. ( It appears that you must be part >of that *special* group on all servers for the Client to "get it >right". After all the UT "Options" do not appear to apply to a >specific server, but to the session of the UT.) > >HTH. > >-- >Carey Matthew Black > >On 2/14/07, Mike Parker <[EMAIL PROTECTED]> wrote: >>Good Morning everyone: >> >>I was attempting to do some troubleshooting of ITSM 7, and I turned on my >>AL >>& Filter logging on the User tool. >> >>When I went to look at the log, I was unpleasantly suprized to find that >>the >>only thing in the log was active links, and no filter logging whatsoever. >>I >>had to turn on filter logging from the Admin tool and get the filter >>logging >>on the server to troubleshoot. I am an ARS administrator on this server, >>and I have Client Side Logging = "Public" >> >>While this is a workaround, this is not an acceptable solution. >> >>Has anyone else experienced this? >> >>User Tool = 7.01 (no patch) >>AR Server 7.01 p1
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
