Use OIR to force object creation in a particular Library context

Ben,

Have you considered simplier solution of using Policy Administration, consider a DENY Access Control for the SubType in the Libraries that should not have the Documents.

I am not a fan of Deny, but in your case it could do what you need it to do.

If using Product Level ACLs or OrgLevel Object Based then you can also leave Role Empty related to Documents and noone can check in to the particular libraries.

Brian Sullivan

Thanks for the reply, Brian. I hadn't thought about using Deny for the sub-types at the library level, but that would work. It would be nicer if we could do a 'move' action from one library to another, though. Is there a way to do that through the workflow? We have the documents tied to workflows for process control and automation. I know that admins and library managers can move objects from one library to another, so it seems like that functionality should be something you could automate upon document creation.

Benjamin Wilcox – IntelliServ^™

PPM & PDM Administrator

IntelliServ provides broadband networking and along-string
evaluation services for high-definition downhole and sub-surface operations > Get the Facts.