Yes, people belonging to a special team should be restricted from public access 
to entries. Not only for Incidents, I guess also for CI's...Problems, Changes...

They need access to the different companies we have, so therefore the company 
restriction does not work.

Maybe more easy to take down the sun than configure this...:)

// Lars

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Misi Mladoniczky
Sent: Friday, October 23, 2015 11:25 AM
To: arslist@ARSLIST.ORG
Subject: Re: Row level access in ITSM

Hi,

When we discussed this earlier I understood that the group you want to give 
limited access is an external Vendor.

Field 60900 is called Vendor Assignee Group, which seems to imply that it is 
intended for this.

What is also important is that 112 is not set to Public, as this would prevent 
field 60900 to have any affect for those tickets.

Note that I have very limited knowledge about ITSM, and what can be configured. 
I have just looked at the permissions on field id 1 and a little on the 
workflow attached to field 112 and 60900. To me it seems that someone intended 
the OOB functionality to work exactly as you desired, but I do not know if it 
all got implemented...

        Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)

Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13):
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.

> Hi,
>
> I have worked on row level access where company A can not see 
> incidents of company B. To do that you have to do customization very 
> carefully so that it doesnt break other functionality which is dependent on 
> that.
> You can work with two fields , 112 and 60900 which is used for row 
> level access. there are few workflows which sets the company 
> permission group ids into this fields and you can have look at the 
> logs and alter the workflow based on you need.
>
> Regards,
> Jayesh
>
> On Thu, Oct 22, 2015 at 1:25 PM, <lars.j.petters...@vattenfall.com> wrote:
>
>> **
>>
>> Hi, we have an ARS system built ourselves, where we have implemented 
>> Row Level Access by changing permission for field 1 and using dynamic groups.
>>
>> This makes it possible to only allow access for users to entries that 
>> they are allowed to see.
>>
>>
>>
>> In our ITSM system, all Incidents for example can be accessed by all 
>> users. We have no possibility to use company restrictions.
>>
>>
>>
>> I wonder if anyone has been able to implement row level access in 
>> ITSM as described? If so, how did you solve it?
>>
>>
>>
>> Best regards, Lars, Vattenfall Sweden.
>>
>>
>>
>>
>> _ARSlist: "Where the Answers Are" and have been for 20 years_
>
> ______________________________________________________________________
> _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org 
> "Where the Answers Are, and have been for 20 years"
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers 
Are, and have been for 20 years"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to