No customization in Webtop. User is having contributor privilege. While importing any document type is disabled. But from DA no such restriction, DATA Dictionary job got locked. Unlock it but in Webtop problem persists.
Try stopping application server hosting webtop
Clearing DFC caches
Restart and retest import
Newly created users dont have such issue. Only problem with the users who were created before.
Are ye using presets?
Can you post a screenshot?
No, we are not using presets. dont have much idea how preset works, can u pls tell me how to identify if preset is already implemented.
Hi Johnny,
This is very strange behavior.
Apology, as this is related to customer so unable to share screen shot. Do you have any idea? why this is happening. there is no customisation done in Webtop.
"Newly created users dont have such issue. Only problem with the users who were created before."
- So what was the event (or is it a date) that old users are having problems, but new users dont?
Let me share you the details of the problem
User X is having - Contributor privilege and rest of the privilege is none. X is assgined to a group Y and Group Y added in a ACL Z and set Y as a write permission. Now say ACL Z is tagged with Folder A.
Now If user X is trying to upload new documents in Folder A , Type Drop down list is disabled and by default custom object is seleted. User is unable to choose new object type.
If User Y is created and assigned to Group Y then if Y is trying to import any document in Folder A then Type Drop down is enabled Y can choose any type.
This is very strange behavior. We have no cusmozation as far as Webtop is concerned.
Have you tried dumping (via API) both user X and user Y to see make sure that all the relevant attributes are the same?
Yes they are almost same. Only difference is one is LDAP user another is inline password user.
Has the customer tried to redeploy webtop? Make sure they delete the app server cache.
You migth still want to double check. I had exactly the same issue at a customer who happens to have a (bad) sys administrator, on top of me for support/administration.
The guy was 'playing aroubnd' with presets to see what they were and he create a preset and by "accident", added a wrong group to this preset, suddenly, all users from this group were stuck and couldn;t do much in the docbase anymore. After a lot of hours trying to find out what was happening, he contacted me and I found this out, removed his preset and then it worked again
Thank you Francois Dauberlieu. Problem is because of PRESET only. We have updated it . Thanks again.
