Create a separate Access Control for Searches

[jwagh]

We would like our users to stop using old and incorrect library models. If we restrict their access to those models, old assemblies that were using them will fail, when trying to open. These old assemblies will not be able to retrieve those library models. This is not what we want. We want users to not find, or view the old models in WindChill, but at the same time, the legacy products to not fail and retrieve them in Creo.

Thank you!

[BenLoosli]

Are these legacy models older versions or different part numbers?

As the first step, I would move all of the obsolete models to a separate folder in the library. Give them read only rights to the folder. This should prevent the models from showing in a search, but still allow them to be loaded in an assembly.

Educate your users that if the have a part from that folder in their assembly, they need to replace it. You should be able to write a custom view of a workspace that shows the folder that contains the file.

[jwagh]

They would be completely rebuilt models - from the bottom up, using a different set of rules. In order to maintain the legacy assemblies, we are just renaming the old models instead of creating new versions/iterations.

I've spoken with support and tested it a few times; the READ access is tied to the search, everything else is not. In essence, you can access the files and search for them or you can't access the files and can't search for them - not one or the other. If you can find a way to get this to work that would be great! I couldn't.

We have checklists, custom views, checking mapkeys that can change the model tree to show windchill data... etc - the whole 9 yards. The problem is that there is no checking system in place that enforces any of the rules. This is a completely separate discussion that has to be done offline.. lol.

[BenLoosli]

" there is no checking system in place that enforces any of the rules "

Have you tried ModelCheck?

[jwagh]

We've implemented modelcheck and added it to our 'checking mapkey'. For this situation, Modelcheck doesn't look for it. And there is no enforcement on the modelcheck rules either. So what if there are geometry checks, frozen models, circular references?... the list goes on and on

[JeffZemsky]

Another option would be to set their Lifecycle state to something like "Obsolete".  You could then use the Lifecycle Check Business Rule in your Change Mgmt process to prevent the user from releasing the assembly with these parts.

Ideally we would be able to plug this into other Action Validators so that it would prevent one from adding these CAD Docs with a state of "Obsolete" into a memberlink.  This is on our roadmap, but I don't have a target release for it at this point.

[jwagh]

Jeffrey,

Thank you for this idea. I will bring it up the chain, but I have a feeling this will quickly be rejected. We work in a very fast-paced company and unless there is something obviously critical, the project shouldn't be held up from release. There has already been some scenarios of users releasing drawings outside of WindChill, I would not like this trend to grow.