Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Content Management (Extended ECM)
API, SDK, REST and Web Services
Retrieving rights from a task
x-idsnro01user2_-_(deleted)
I am trying to get the permissions on a task item in our system. From what I can tell, LL_ListRights is always returning full access for everyone. However, the permissions on the task list in the system show much more restricted permissions. This is also indicated by the fact that only a few users can see this task when they issue a search. My question is, how can I get the true permissions for the task? Do I need to get the permissions of the task list and apply those to the individual task items? What about any attached documents in the task? Finally, how would I go about getting the rights to the parent when I am given the Volume ID and Object ID to the task item (ParentID is simply -VolumeID when I call getObjectInfo -- passing this into LL_ListRights returns full access again). This is on 9.1.0.3, using C++ libraries. Thanks!
Find more posts tagged with
Comments
x-idsnro01user2_-_(deleted)
OK, I have also just disccovered the PermID field from GetObjectInfo. However, this just gives me the parent's object ID. In order to get the rights from the parent, I still need the parent's volume ID, correct? If so, how do I go about getting that when all I have is the child's object and volume IDs? Thanks!
Rolf_Poser_(sbsuser06_-_(deleted))
Dunno whether this might help - had a similar problem with the volumeID of attachments - these are in a different volumeID to the enterprise.Anyway, one of the ways I could get "GetObjectInfo" forced into reading my attachment was to specify a volumeID of 0.Use with care, since I haven't had any confirmation from support that this method is bulletproof.I don't see a special volumeID for tasks in my DTREE, so tasks are probably normal. (There is one for the Workflow volume..)Good luck, and let us know how you managed to work around this.Thanks,Rolf.