Adding rights in Documentum via Webtop

Is there an easy way to add new rights in Documentum? I have a folder and subfolders where I have to add a new user to have modify rights to all these files. Is there a DQL command I can use to add rights? Rights are not inherited in Documentum as far as I know.

Find more posts tagged with

Comments

Francois Dauberlieu

try something like update dm_document objects set acl_name='sdfsfsf',acl_domain='sxdfsdff' where folder('/mycab/myfol',descend)

where the acl_domain is the owner of the acl.

kjimenez

I tried that, my query looked like this:

update dm_document objects set acl_name='testacl',acl_domain='Docu_Rep' where folder('/Temp',descend)

and I get the following error:

Error occured during query execution :[DM_QUERY_E_SYNTAX]error: "A Parser Error (syntax error) has occurred in the vicinity of: update dm_document objects set acl_name='testacl',acl_domain"

If I run it without the acl_domain argument I get the error it was unable to fetch the domain

Francois Dauberlieu

Try update dm_document objects set acl_name='sdfsfsf', set acl_domain='sxdfsdff' where folder('/mycab/myfol',descend)

I'm not a DQL/SQL expert so the syntax might still be wrong. Check in the DQL guide

Wiesnoepersad

The correct syntax is:

update dm_document objects

set acl_name='sdfsfsf'

set acl_domain='sxdfsdff'

where folder('/mycab/myfol',descend)

There is no ',' comma between the sets.

Better to update all versions (i.e. update dm_document(ALL))

baixench

I make my "Updates" with "," between fields and it works

kjimenez

I was able to do this in QA, but when I ran it on our Prod environment with much more files I got the folliwing error

Error occured during query execution :[DM_QUERY_F_UP_SAVE]fatal: "UPDATE: An error has occurred during a save operation."

[DM_SYSOBJECT_E_CANT_FETCH_ACL]error: "Failed to fetch the ACL 'mip' in domain 'user1doc' for dm_document 'Analysis.doc'. [ProcessACL]"

[DM_ACL_E_CANT_FETCH_ACL]error: "Failed to fetch the ACL 'uae' in the domain 'user1doc'."

It seems like this is because the owner of files doesn't exist. I am trying to run a query that will change the owner to an active owner. I am getting all kinds of lock errors though, what would the DQL look like to cancel all locks? is it just changing the value of r_lock_owner ?

Francois Dauberlieu

Would be better to use the unlock API statement, that way the users will be notified that their checked out documents have been released, otherwise, that might come as a surprise to them and you'll most likely get your back side kicked big times

Actually, the best, would be to let your user community know that due to maintenance of the system, they should check in or cancel the check out of all their checked out documents before a certain date/time ad at this date/time, they will be automatically unlocked and the maintenance will be performed. I say that because it might not be well received by the users that such an important thing happens in their production system (don't forget, you might be the administrator but it is their system and if they all start complaining about you, your job will be on the line not the jobs of all your users) without them being warned beforehand. In my experience, users don't like their locked documents to be unlocked without being warned beforehand.

The last thing you want is have all your users on your back...

kjimenez

Actually I only want to unlock files that are locked by a user who is no longer with the company. So It should be find. I figured it out I think. It is jsut taking a long time for the query to run.

Wiesnoepersad

select r_object_id, object_name, r_lock_owner, r_lock_date, r_lock_machine

from dm_document where folder ('/Temp',descend) and r_lock_onwer='<user who left company>'

will give you overview of all documents locked by <user who left company> in the folder "tempd" and who locked, on which machine..