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
Propagating node creation restrictions down a tree structure
Anquoc_Tran
I am creating a new container node called "Case". The Case node can only contain documents and folders.Within a Case node, I only want documents to be stored, which may be arranged in folders and sub-folders. It is of course easy to set up the Case node so that only documents and folders can be added within it using the fChildSubTypes and/or fChildApplTypes features.However, if a folder is then created *within a Case*, it is still possible to create other nodes (such as projects, discussions, tasks, etc.) in the new folder, which I want to disable. If a folder is created outside of a Case node(where there is no "grandparent", or "great-grandparent" Case), I still want these features to be enabled.My question is this: how can I propagate this restriction down a folder hierarchy *within a Case*, so that my Case can only contain documents arranged in folders?One possible solution I have considered is to create a new "Folder2" node, identical to a Folder, but with a different SubType/ApplType, and then to only allow this new Folder2 node to contain other Folder2 nodes and documents. Is this the only way, or can somebody suggest an alternative method?I am using Livelink version 9.1.Any help appreciated - thanks in advance.
Find more posts tagged with
Comments
There are no comments yet