Perhaps a better solution would be to make the Status field RO, and have the status of a record advanced with buttons that would be enabled under conditions defined by workflow. Both the buttons and the Active Links behind them can have different permissions, so that advancing to different status values could have different work rules for different groups.
It's potentially a lot of work to set up, but would do the job. Another way that might be less functional, but is also less work, would be to have the visibility of the field (RW vs. RO) be affected by different Active Links (change fields actions) depending on the Group membership of the user. That would lock a group from changing the status FROM a value, but only workflow could define what it could be changed TO. Rick -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Thursday, May 31, 2007 9:50 AM To: [email protected] Subject: Re: Hiding Status Values Ashley, My guess is that the requirement has more to do with allowing some users to change the status to some limited values. ( But I could be making to many assumptions here too. :) If that is the case.... Then you could go with a new field that gives the user a char field with a search menu from data that is restricted by the same "row level access group" logic. That way the users interact with this new field to "change the status" and you let a filter move the value from the new field to the real Status field. However, as Ron pointed out, if the user actually has access to the Status field itself, then the users will have access to the Status History data too. If that is the real issue, then you have to remove the users access to the real Status (field ID 7) field in order to block access to the Status History data. Yes you could remove that "Menu option" from the view, but that is not "row level access" restricted and would not actually block the user from doing a report and seeing the data either. So maybe you could better describe the desired end state and get a few more ideas about how you could do something like what your trying to do? -- 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 5/31/07, Axton <[EMAIL PROTECTED]> wrote: > With a drop down (enum) field type? Not gonna happen. > > Axton Grams > > On 5/30/07, Ashley Henderson <[EMAIL PROTECTED]> wrote: > > ** > > > > LIST, > > > > Anyone out there have a suggestion on how to hide status values for > > a particular row level access group? > > > > Remedy Version 6.3 ____________________________________________________________________________ ___ 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"
