cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Need separate columns for locked status and checked-out status in Windchill Workspace

Need separate columns for locked status and checked-out status in Windchill Workspace

Need separate columns for locked status and checked-out status in Windchill Workspace. Currently it is part of General Status column where checked-out symbol is shown when that object is checked-out by logged-in user or any other user. But when we use preference setting Automatically lock objects added to workspace set to YES, the status of objects is shown with lock symbol overwriting checked-out symbol if that object is checked-out by some other user and not by logged-in user.

We are using Windchill 10.2 M030-CPS08  and we have preference setting for Automatically lock objects added to workspace set to YES.

But we are facing issue with objects which are checked-out by some other user but it does not shows the checked-out status if object is locked in workspace. Here it is overwriting check-out symbol by locked symbol. So user are not able to recognize if the object they are using is being modified by someone else or not, hence sometime users are using out dated or non-latest iteration of the objects in their assemblies.

So if anyone wants to see if any object is checked-out by someone else, user need to manually unlock all objects and see the status which is time consuming activity.

Here we propose to have either 2 separate columns one for locked status and other for checked-out status of an object or if with single column checked-out status should have precedence over lock, It means even object is checked-out by some other user, status should show checked-out symbol and not the lock symbol.

Plz refer attached images for more information.

Below is the preference I am talking about.Name  :  Automatically lock objects added to workspace

Description  :  Set workspace lock default to automatically lock all objects that are not being checked out during Add to Workspace and Checkout operations.

No - (Default) - workspace lock is not set on objects added to the workspace and not checked out

Yes - workspace lock is set on all objects added to the workspace that are not checked out

3 Comments
Topaz II

Ravindra Mane

You may want to vote on your own idea....   

Granite

 Need to move this idea under Windchill Ideas topic to get more votes as its related to Creo-Windchill Data Managment topic.

We are also facing the issue and user need to unlock all items to check the checked out by status which is not good practice.

 

 

 

 

This deficiency prohibits co-creation and development amongst engineering team members.

Please take it under serious consideration.