Draw back of Authority List
2 posters
Page 1 of 1
Re: Draw back of Authority List
I would see the fact that an object can only be secured by one authorisation list as the difficult point in using them. We need to have a good starting plan about seperating authorities with authorisation lists.
When we first attach an authorization list to an object, the object must be allocated exclusively but then after the authorization list is attached, we can add change and remove users from the authorization list at any time without needing to get an exclusive lock on the objects assigned to that authorization list.
That is the biggest advantage over assigning individual authority to the object.
When we first attach an authorization list to an object, the object must be allocated exclusively but then after the authorization list is attached, we can add change and remove users from the authorization list at any time without needing to get an exclusive lock on the objects assigned to that authorization list.
That is the biggest advantage over assigning individual authority to the object.
sivakumar- Posts : 174
Join date : 2009-07-27
Age : 37
Location : Chennai
Similar topics
» What is Primary Group Authority?
» test object and data authority
» New Security feature in V7R3 - Authority Collection
» Library List
» List various SYNON/2E Relations.
» test object and data authority
» New Security feature in V7R3 - Authority Collection
» Library List
» List various SYNON/2E Relations.
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|