Skip to main content
J
jhall21-Visitor
1-Visitor
August 26, 2016
Question

How to lock CAD objects

  • August 26, 2016
  • 3 replies
  • 4095 views


Greetings

We are using Creo 2.0 and Windchill 10.2

We need to occasionally create CAD models that are lightweight representations of complex assemblies.  We want to use these so called dummy models in other assemblies and drawings.

The question is, is there a way to lock these files in Windchill?  We are going to have a naming and storage convention for them, but we don't want them Released, just somehow locked.

Any ideas?

Thanks, James Hall


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

3 replies

T
23-Emerald IV
TomU23-Emerald IV
23-Emerald IV
August 26, 2016

You can control changes to them by permissions on the context or by permissions on the lifecycle state.  The context is probably easier, but if it's more logical to keep them in the same location as the files they are built from then an extra lifecycle state probably makes more sense.  Out of the box there is "Obsolete".  Normal users can view objects at this state but are not allowed to revise or check them out.  It sounds like you are looking for the exact same thing but with a different name.

S
21-Topaz I
STEVEG21-Topaz I
21-Topaz I
August 26, 2016

You beat me by a hair.

S
21-Topaz I
STEVEG21-Topaz I
21-Topaz I
August 26, 2016

How many files are you talking about?  You could create a Library context for these objects.  Then set the rights so that nobody except the admin or someone else has rights on it.

J
jhall21-VisitorAuthor
1-Visitor
August 26, 2016

Library is pretty interesting.

So, let's say we call these dummy objects.  We drop them into the dummy object folder?  Then give it a library sort of context?

I think we want the designer who made them to have access to unlocking their own, not just the admin..

Good discussion, guys, thanks

S
21-Topaz I
STEVEG21-Topaz I
21-Topaz I
August 26, 2016

Unfortunately, as far as I know PDMLink doesn't have something that Windows has.  A group called CREATOR OWNER.  I have set 1 or 2 directories on the network such that the only person that can delete, overwrite a file is the person that created it.

T
23-Emerald IV
TomU23-Emerald IV
23-Emerald IV
August 26, 2016

It would be good to clarify if you are trying to prevent inadvertent changes (by anyone) or if you want to absolutely prohibit changes by anyone other than the creator.

J
jhall21-VisitorAuthor
1-Visitor
August 26, 2016

Tom,

We are wanting to prevent inadvertent changes that would affect what the creator used the original file for. That's a great question.

Currently they are In Work, and subject to editing by anyone.  We create them, and then later find them hacked up by designers all over the world.

T
23-Emerald IV
TomU23-Emerald IV
23-Emerald IV
August 26, 2016

What does your release "process" look like today?  Does everything stay at work, or are objects being changed to other lifecycle states when completed?  (Knowing what you're doing now may help determine the best approach for your environment...)

Terms & ConditionsCookie settingsAccessibility statement