PermsApplyDown vs SimplePermsApplyDown

Hi,

Can anyone tell me what the difference is between doc.PermsApplyDown and doc.SimplePermsApplyDown? These are request handlers in the WebDoc ospace. I'm just trying to understand if they behave differently, and if so, how.

Thanks

-Hugh Ferguson

Find more posts tagged with

Comments

eLink User

SimplePerms when you select a User or a Group and push the permissions to Self and children targeting the single ACL entry you have.

In the other one you are selecting the javascript function that looks like a padlock with an environmental(green) twist.Right after the Object

The popup now loads a page that will allow you to change multiple ACL entries .Note this command can Add,Remove Clear ACl's,Make somebody owner

etc etc.Massive ways of adjusting perms from a container down.

.....appu appnair appunair

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Tue, Mar 8, 2016 at 3:02 PM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

PermsApplyDown vs SimplePermsApplyDown Posted byFerguson, HughOn 03/08/2016 03:57 PM

Hi, Can anyone tell me what the difference is between doc.PermsApplyDown and doc.SimplePermsApplyDown? These are request handlers in the WebDoc ospace. I'm just trying to understand if they behave differently, and if so, how.Thanks-Hugh Ferguson
[To post a comment, use the normal reply function]
Forum: Content Server Development Forum
Content Server: Knowledge Center

image.png

HFCDev

Thanks for the info....

I think I found a race condition with the SimpleApplyPermsDown series. First, I noticed that when you are pushing a new group down from a top level folder, it does one node crawl to add the record, then another node crawl to update the rightID to the correct permissions.

In this case, I observed it in both SimpleApplyPermsDown3 scripts do a Select on DTreeACL and not find the user/group in question and add it, creating a duplicate ACL on one of the child folders.

To OT: We have a ticket open and I will shortly be sending log files. Is there any reason why two separate node crawls are done? Why not add the record with the desired rights immediately rather than doing as a two-stage with separate node crawls? In the case I isolated, that by sheer concidence, the two node crawls ended up doing an update on a sub-item's DTreeACL at exactly the same time, which would explain why the second one never saw that the first one had added the record already and also did an insert.

-Hugh