WebTop: New Document is disabled despite the user has necessary permissions

GlenLantz

I have met the following weird behavior of WebTop:

I have Documentum Developer Edition 6.6 installed
I have created a user named User1; it has no Privileges
I have created (as Admin) a cabinet. I have added Permission: Delete for the User1 and the cabinet
I log into WebTop as the User1 and try to create a document in the cabinet. I cannot do it – File->New->Document in the WebTop is disabled. Why? If I open Properties of the cabinet in WebTop as User1, I see ‘Your permissions: Delete’. In other words, the Permissions for the User1 are enough to create a document. So what is it – WebTop bug?

Find more posts tagged with

Comments

DCTM_Guru

No, this is not a Webtop bug.

"I have created a user named User1; it has no Privileges" - which means the user is "consumer" type, which means the user has read-only privileges in the repository. If you want the user to import/modify content, you need to give the user at least "contributor" privileges.

GlenLantz

Yes, I see you are right. With the following correction: the Consumer, Contributor etc are not Pivileges but Client Capabilities:

“EMC® Documentum® Documentum Administrator Version 6.6 User Guide”

…

Client Capability

Describes the expertise level of the user.

The client capability setting is used by Documentum client products,

such as Webtop, to determine which functionality to deliver to the

user. Content Server does not recognize or use the client capability

setting. For information about the client features available with each

setting, refer to the Documentum client documentation.

Choose a user type from the list:

• Consumer

• Contributor

• Coordinator

• System Administrator

…

Thus, the Client Capability is just a GUI filter atop of the Content Server. If I will try to create a Document in the described situation using DFS/DFC/…., the Content Server should not forbid it. I have not tried this yet; but I will try later – to be 100% sure.

lastnitescurry

 just a GUI filter atop of the Content Server

no it is not just a GUI Filter... it has impact on licencing

GlenLantz

really? could you please explain?

lastnitescurry

no, because your endless questions annoy me. its long past time you did some work yourself, like read a few manuals and shell out for some documentum courses

DCTM_Guru

From a licensing perspective, if you were sold read-only access, you do NOT have right ("license") to enable content contribution (ie contributor or above access), even you can do this programmatically.

The enforcement of this is done at the UI layer - more specifically at the web application layer (not Content Server layer).