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

We are happy to announce the new Windchill Customization board! Learn more.

Prevent Check-in of objects into Wrong context

Devidas
9-Granite

Prevent Check-in of objects into Wrong context

I am having windchilll site which using different version scheme for different context. One of context using the Numeric series like 01, 02, 03, .......99. and another context using the series like -, A, B, C, ........... etc.

The major problem we are facing now is some of the users select the wrong workspace and create the CAD document and save & upload to workspace, so system assign the version series value as per that workspace context.

During check-in users realize that they have selected the wrong workspace so they change the location to correct context during check-in.

This operation moves object to correct context but it version value remains incorrect or as per workspace context in which it created.

Example :

Product- A --> With version series 01, 02, 03,.....

Product-B --> With version series A, B, C, .....

1. Task is to create the Block.prt in Product B with version series A as First version.

2. By Mistake User Creates the CAD part Block.prt in Product A workspace so system assigns the version series 01 during upload of that object. During check-in or after check-in user realizes that location is inocrrect and user set the location to Product-B or moves object to correct context after check-in.

I am looking for the solution which will restrict user to check-in into wrong context and will prompt some message warning message. Any solution to restrict this will be welcome.

We have subfolder structure in every context so we cannot set the default check-in location for every context.

Thanks in Advance.

2 REPLIES 2
sgudale
10-Marble
(To:Devidas)

Is it required for all users to have access to all contexts in your orgnization? If not then add deny to modify and modify contents for other contexts so that users will only be able to read and not modify or check in.

Thanks,
Shivprasad
Devidas
9-Granite
(To:sgudale)

No, We cannot deny the access because user need access to both the version series context.

Top Tags