NX Managed NX2212 no longer enforces the NX Environment security locking of data

Prior to NX 2212, NX Environment setting provides security tagging that automatically ties the NX data saved to the specific NX environment that was launched, so the data is automatically secured within that specific environment. And if you run NX using a different environment, you are blocked from performing operations on the same design data.

Now in NX2212 and newer, this security tagging behavior no longer works, as the NX data is not automatically secured within its specific environment. How to setup the security tagging behavior in NX2212 and newer?

The new TC_NX_Environments_Secure Teamcenter preference lets you specify the environments that apply security tagging, so you can now launch an environment that has no security tagging. If an environment is not listed in the preference, it does not require security tagging.

If you run NX using secure environments, which require security tagging, and unsecure environments, which do not require security tagging, the following apply to your design data:

Saved in a secure environment, you can modify it in that same environment.

Saved in a secure environment, you cannot modify it in a different secure environment.

Saved in a secure environment, you cannot modify it in an unsecure environment.

Saved in an unsecure environment, you can modify it in a secure environment.

The available environments that you can use in the TC_NX_Environments_Secure preference are listed in the TC_NX_Environments preference.