repository owner not able to modify permission on document

anu1

Hi,

I have created a workflow with a auto activity which runs an automatic method on behalf of repository owner.

Below is snippet to modify existing ACL:

object.grant(session.getLoginUserName(), 6, null);

for(int i=0;i<userName.size();i++){

if(object.getPermitEx(userName.get(i))<6){

object.grant(userName.get(i), 6, null);

}

else if(object.getPermitEx(userName.get(i))<3){

object.grant(userName.get(i), 3, null);

}

But the permissions on document are different.

Please let me know.

Thank You.

Find more posts tagged with

Documentum

Comments

DCTM_Guru

Did you execute object.save()? Not sure if grant() does explicit save.

bacham2

Good point Johnny: no, it doesn't save explicitely.

By the way, do you realise that your code will create an internal ACL each time it is executed? I don't know what your requirements are but this is not considered best practice. If your code is executed a lot, you will end up with one ACL per document in the worst case. Better to define a finite set of ACLs and keep reusing them.

DCTM_Guru

Bacham brought up good point about ACLs, if you have millions of docs = millions of ACLs = this will impact performance of the server.

anu1

Hi all,

Thanks for your reply.

Yes object.save() is happening after changing permissions.

The requirement is such way that ACL's are to be created on fly i.e internal ACL's.

The method is part of workflow auto activity and performer is Repository owner.

Folder Security is on and User is default ACL inheritance.

What all things I need to check to debug the issue further.

Thank You.

DCTM_Guru

How are you verifying that the permissions are different? I would put logging statements verifying that the object you are modifying is the same object you are verifying permissions against.

anu1

Hi,

Thanks for all your help.Its assigning correctly now and it was due to incorrect permissions for user who was modifying.Repository owner was not selected as performer.

Thank You.