Automatic lock componets when opening an assembly (See Case 12415387)

[BillyCarwile]

Windchill‌

When opening an assembly with the preface set to automatic
lock objects on add to workspace. PDMLINK does lock all components. When
opening an assembly from local drive and components are in PDMLINK with server
turn on PDMLINK does not lock any of the components.

Case Reference: [ref:_00DA0YLPa._500F0WawuQ:ref]

Case Subject: With Prefernce (Automatically lock objects added to
workspace)set to YES. Does not lock objects that are downloaded to workspace
when opening an assembly from a network drive. The assembly is using parts from
PDMLINK.

Hi Billy,

This case is assigned to me. I tried replicating the use case and found
it to be reproducible.

Objects available on Windchill server doesn’t get locked , when you are
retrieving the copy of  assembly from local disk. This is the current
behaviour Windchill PDMlink.

“Automatically lock objects added to workspace” preference works with
explicit “Add to Workspace” command.

Even if you open any assembly  from Windchill via File ->Open,
then also locking of object doesn’t happen.

The functionality that you are looking for is currently not available,
this would be considered as enhancement on the product. Please feel free to add
weight to this requirement through Enhancement Logger @ http://support.ptc.com/support/PTC_Product_Ideas.htm

Sincerely,
Anu

[delcampo95]

We have recently encountered a big efficiency loss for a workforce of 1500 Creo users related to this issue.  Our characterization of the symptoms are: 

When a component, which exists in Windchill Commonspace is placed into an assembly it is automatically added to the workspace. Currently, these placed components are not being added to the workspace in a "locked" state. This creates an opportunity for these components to be modified in the workspace and cause failures during Check In.​  This results in users having to perform a painful workaround to finally Check In.

We also understand that there is currently no configuration setting to "Automatically lock components when added to assembly".  I will definitely be voting for this enhancement right now.

[Chris3]

Actually there is such an option. Its a windchill option.

Quick Links -> Settings -> Preferences -> Workspace -> Add to Workspace and Check Out -> Automatically lock objects added to workspace set to yes

[delcampo95]

Chris3: apparently this is the option that we already have selected, which works fine if you add parts via Windchill.   It doesn’t help when we’re accessing them from a network/local location even though they exist in Windchill and the common space which is the case for our library parts.  So maybe what we need is:

 Automatically lock objects added to workspace from network location

[Chris3]

@delcampo95 This sounds like a business problem. Why are you pulling files from a network location?

Windchill will not know if the network files are different from the PDM files (how could it) and whether or not you want to use the local / network files instead of the PDM files. Thinking through the broader use case where a user wanted a non-library part to iterate over the PDM part somehow locking those parts would then be a problem for them.

Sounds to me like you need to just stop maintaining library files on network folders.