NX Non-writable (Released) data is checked out by TCNX operation.

Non-writable (Released) data is checked out by TCNX operation.


There is UGMASTER data for which the owner has set access rights that are not writable.
If you change the access right setting so that the owner can check-in / out, the data is checked out when you edit the data on TCNX.
 
 
Steps to Duplicate:
========================================
 
1.Create a new item in NX
2.Assign release status to UGMASTER data.
3.Change access rules in Access Manager.
  Changed "Owing User" checkout/check-in of "Has Class (POM_aplication_object)-> Working" to TRUE.
4. Open and edit UGMASTER data in NX. (Editing is not applied because it is released data)
5. Check the UGMASTER data on TC. It turns out that you have been checked out.

Solution

If the "TC_Auto_Checkout" preference is ON, non-NX datasets will be automatically Checked-Out when a user opens that dataset. This will prevent another user from gaining write access to this dataset until the first user closes the dataset.
 
So, this preference will not impact the UGMASTER dataset. Refer below snap -
 

Also, as we are providing checkout/check-in access using below-
Change access rules in Access Manager.
  Changed "Owing User" checkout/checkin of "Has Class (POM_aplication_object)-> Working"
 
 
If you remove the access then the issue of released UGMASTER getting check-out will not appear.
 
Also, the reason behind released UGMASTER getting check-out from NX after modification because as mentioned above you are providing access on "checkout/check-in" and along with that under NX Customer Defaults any of the below Check-out/Check-in Policy option are set-
 
 
 
·           Automatic Check-out on Modify or Save; Check-in on Save/Close
When you modify a part, NX checks it out automatically. When you save or close the part, NX checks it out (if it has not been already) and checks it in automatically.
·           Automatic Check-out on Modify or Save; Check-in on Close
When you modify or save a part, NX checks it out automatically. When you close parts, they are automatically checked in. This is the default setting.
 
 

 


So, this is working as designed as you are providing access to "checkout/check-in" in Access Manager and when data is getting modified from NX, it will get checked-out.
 
However, if you do not want to checked-out the NX dataset from NX though you are providing access checkout/check-in" in Access Manager then you must use below Check-out/Check-in Policyoption in NX -
 
·           Automatic Check-out on Save; Check-in on Save
·           Manual Check-out Required for Save; Manual Check-in
·           Manual Check-out Required for Save; Check-in on Close
 
Also, if you still want to use below Check-out/Check-in Policy option in NX and want to keep the same setting in Access Manager for checkout/check-in of Has Class (POM_aplication_object)-> Working" to TRUE.
 
 
·           Automatic Check-out on Modify or Save; Check-in on Save/Close
·           Automatic Check-out on Modify or Save; Check-in on Close
 
Then, in this case, if you do not want NX to Check-out the dataset then you may modify the below changes in Access Manager -
 
Change access rules in Access Manager.
  Changed "World" checkout/check-in of "Has Status (TCM Release)-> TCM Release Rule" to FALSE.
 
See below snap-

 

Notes and References

9747898

Hardware/Software Configuration

Platform: INTL64
OS: windows
OS Version: 1064
Product: NX
Application: NXMANAGER
Version: V1946.4000
Function: LOCKING

Ref: 002-8510605