nirie1 - Tuesday, August 24, 2010 5:27 PM:
We would like to restrict access to certain types of parts (ie restricted). We would the people that have access to this inforamtion to have access to nonrestricted parts as well since restricted and non-restricted parts often have parts in common when looking at assemblies.
There is some divergence of thought here on our Aras team. One school of thought is to create a totally new item type called restriced parts but the concern is permissions, access, running reports, etc.
Another school of thought is to make restricted parts a subset of parts item type. And the final thought is to add a field to the parts form called restricted that with some programming surrounding permssions will only allow those with access to restricted to view restricted items.
Any thoughts, tips or views?
dbqw - Tuesday, August 24, 2010 6:24 PM:
I'm trying to do something similar. I'm intending to use a property patterned after owned_by_id to control access. The idea is that you add a property to the Part item type that allows you to select an access list from Identities. Then you just delete "All employees" from the Part permission and add your new property. The problem is that I can't figure out how the owned_by_id works. It somehow connects the Identity you choose to another identity called Owner which is on the Permission. I can't figure out how that linking is done. BUT, you can just "steal" the owned_by_id and use it for your access lists if can do without it otherwise.
Ron - Monday, August 30, 2010 1:08 PM:
Hi Nirie1
xueron564 - Sunday, August 14, 2011 8:53 PM:
888xuerong-3:
francissdo - Tuesday, August 31, 2010 2:06 PM:
I like the idea of using different life cycle map to set separate permission for the released stage, of the restricted document, based on classification. However, I've tried to implement that and gotten an error regarding "No items of type Document found."
Additionally, I do not know whether it is neccessary to set permission for file, since file is not directly accessible by users. This could be a challenge to set permission on file. It means that we have to build different file loading interface to accept restricted/non-restricted access.
