SETTING permanent_link to False - Very Very Urgent

Hi All,

I have an requirement of setting the Permanent_link value to false for all the objects.

Issue:

Once a document is created and flowed to a workflow and the approver rejects the document .

Then the owner of the document is not able to add a new version on the same document which it was rejected in workflow...

So when we take the Log and analyse we found

[DM_RELATION_E_NEED_PRIV]error: "The current user Manikandan Kumaresan has insufficient privileges to save or destroy DM_ANNOTATE relation."; ERRORCODE: 100; NEXT: null

I had f=gone through the object reference manual and

Wat we tried is with the Database Owner permission , we updated the Permanent_link value from dm_relation_s for that particular object alone to be FALSE which was TRUE.

Then the owner tried to version the document , It gets versioned ..

So will this be taken as a fix for all the documents .

so that the user can version the document which is rejeected by the workflow...

Wat are the sideeffects of this solution of setting permananet_link -> FALSE,..

Is this preferable solution?

Kindly suggest me ASAP.....

Find more posts tagged with

Comments

sergi

When permanent_link is set to false, relation will only present with one version of objects. If it set to true, all versions of objects will be related.

As far as priveleges (your error message) - the user should have at least Relate permission on objects.

And, it would be helpfull to check security_type of corresponding dm_relation_type object.

P.S. sorry for my English.

Akmk2787

Thanks for your suggestion ,

As far as i understood , whenever the versioning of an object is happening ,

A relation object is been created in the DM_ANNOTATE relation.

The attributes of the DM_ANNOTATE relation has been defined in dm_relation_type table .

When i queried for that i got the security_type : SYSTEM for the DM_ANNOTATE relation.

So only SysAdmin + Super User can able to create,modify,delete the object in DM_ANNOTATE.

so the current normal users cannot be able to version as this relation is not getting create in the DM_ANNOTATE relation.

So if i change the SECURITY_TYPE:NONE in the dm_relation_type of DM_ANNOTATE.

which will allow all the users to create the relation that happens during versioning.

Is this FIX a valid solution ?

Changing this System table dm_relation_type for that DM_ANNOTATE relation SECURITY_TYPE as NONE will have any adverse effects???????

update dm_relation_type object set security_type = 'NONE' where

relation_name = 'DM_ANNOTATE' and

r_object_id =<<object id of the relation>>;

CAN I RUN THIS DQL TO FIX THE ISSUE ?????

WILL IT AFFECT ANY OTHER THING IN THE ENVIRONMENT???

KINDLY SUGGEST ME ASAP......

sergi

Yes.it will fix your problem, but if you set security_type='NONE', so every user will can update or delete these relations.

And as far as DM_ANNOTATE is system-defined annotation - if you will do upgrade, sesurity_type will be overwite to SYSTEM again.

I advise you to request Documentum tech support about adverse effects.

But i think, this will not seriously affect system (except that i posted above).

P.S. Sorry for my English.

Akmk2787

Upgrade in the sense .

Referring the Content Server upgrades .

Akmk2787

Hi Sergi,

So only when we are Upgrading the Content Servers this attribute will be setted back to SYSTEM right.

Is there any other instances in which this attribute will get reverted back??

sergi

As i know, the value of attribute will reverted back only after upgrade.