Skip to main content
16-Pearl
October 4, 2016
Question

Can the Creo Parametric 3.0 toolkit lock files in session without Windchill?

  • October 4, 2016
  • 1 reply
  • 3420 views

I'd like to be able to lock certain files in a Creo Parametric session similar to how the Windchill workspace lock works.  However, Windchill will not be used.  The make features read only function doesn't provide complete functionality in stopping the user from modifying the models models.  The list of models to "lock" would likely be a simple .txt, .csv, or similar file, and the user could manually lock a model, on the fly so to speak, in session via a menu pick.

So far, most of our "customizations" haven't used toolkit, but we're getting to the point where we can't do what we want without it.

Regards,

Dan N.


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.

1 reply

17-Peridot
October 5, 2016

1) Look at Toolkit User's Guide Event-driven Programming: Notifications. You can abort save file operations

OR

2) Using MS Windows functionality to set file property Read only

dnordin16-PearlAuthor
16-Pearl
October 5, 2016

Yaroslav,

Thanks for the suggestions, however, those options will only prevent the model from being saved.  I was looking to prevent the user from making any model changes in the first place.

The functionality I'm looking for already exists when using Windchill.  I was hoping PTC had the functionality within the Toolkits that would allow files to be locked without Windchill.

Regards,

Dan N.

23-Emerald III
October 5, 2016

Even a read-only file in a Creo session from Windchill can be modified in the Creo session by changing the flag and allowing the changes. The user will still be prevented from checking-in or saving the changes, but nothing prevents them from doing a Save-As to another filename and/or location.