Locked module licenses tied to a floating license

[Chris3]

This is my first time dealing with locked module licenses so I am looking for confirmation that this is true.

If I call a T2 [PROE_DesignAdv] floating license in my psf and I have a locked module license then my understanding is that the psf will look like this:

ENV=CREOPMA_FEATURE_NAME=PROE_DesignAdv (386)

Where 386 is the locked module featurename (in this case Generative Topology Optimization). If I have more than one locked module then there is just a space between then (108 386) for piping and topology for instance.

Do I have this right?

[Chris3]

Also, just to confirm, PTC has locked and floating modules. If I buy a locked module I have been told that I can tie that to a floating base license with the psf. Can someone confirm? So in this case:

PROE_DesignAdv (386)

PROE_DesignAdv is floating, but the module that comes after it () is locked to the floating module. Its confusing because they also use the locked terminology for locking a license to a specific machine which isn't what I want.

[MartinHanak · Accepted solution]

Hi,

yes, you are completely right.

FYI locked module is called Extension.