I think it's still there in 4.5.2. What we saw was that if the data got
into the form via sql rather than via aruser, if the field that is being
complained about has a value of 1 space, or if it is a one-character field
with a blank in it (I forget which, it was something like that), then the
user tool would change that field on display, and set the change flag.
I think it has something to do with Remedy not wanting to store trailing
(leading?) blanks.
In our case we noticed that only certain records have a problem, not all
records. That was because the sql that loaded the form did not always set
the problem field to space (ascii 32), but sometimes it did.
This may have shown up when the data got in via armaild or arimport, too.
Sorry my recollection isn't crystal clear.
Deleting the space in the problem field (as administrator or someone with
permissions on the field) was one way to prevent the non-admin user from
experiencing the problem.
Interestingly, the 3.2 aruser client does not have this bug.
-----Original Message-----
From: Kay Seaman [mailto:kseaman@FAME.COM]
Sent: Wednesday, December 19, 2001 12:19 PM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Permissions question
**
Thanks all for your reply, I believe I have my answer. I was told that
upgrading client to 4.5.2 will do the trick.
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of Roger Nall
Sent: Wednesday, December 19, 2001 1:02 PM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Permissions question
**
Kay,
It sounds like you have some workflow that is changing the value of the
field mentioned in the error. We had the same problem with Display only
fields. We had workflow that would set the value of these fields on display.
We found out that we needed to give all groups change access to these
fields. You may try turning on your filter logs. Also have the client turn
on AL logging. HTH
Roger A. Nall
Project Manager
Remedy Administrator
Covista Communication
888-890-7600x7446
rnall@covista.com
-----Original Message-----
From: Kay Seaman [mailto:kseaman@FAME.COM]
Sent: Wednesday, December 19, 2001 12:49 PM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: FW: Permissions question
**
Has anyone run across a problem with ARS where you want to permission a
group to only certain fields, but when they try to enter data in the
permissioned fields they get an error "You do not have access to field:
Field Name" where field name is not a field we want them to have access to
and Client logging shows the workflow does not depend on this field. It is
not a required field.
Remedy Version is 4.5.01
________________
_____________
You may also control your subscription options, including UNSUBSCRIBE, at
www.ARSLIST.org
________________
_____________
You may also control your subscription options, including UNSUBSCRIBE, at
www.ARSLIST.org
________________
_____________
You may also control your subscription options, including UNSUBSCRIBE, at
www.ARSLIST.org
_____________________________
Previous Topic
Index