Frequently Asked Questions: User Features   

This section gives you information about questions you may have when working with User Features (UDFs).

Using UDFs




Can I insert measures in a UDF?

No, you cannot. Measures are not supported by UDFs, the data structure does not support them.

Can a UDF have a variable number of inputs?

No it cannot.

Can I insert sub-elements into a UDF?

No you cannot. To know which features can be inserted into a UDF, see the What cannot be inserted into a UDF? question.

What is the use of typing a UDF?

Associating a type to a UDF can be useful: It will be available through the Search functionality and will also be available in the Knowledge Expert Browser. To get an example, see Referencing User Features in Search Operations.

When typing a UDF, why must I split the Instance Type into 2 fields?

Instance Type is divided in 2 fields to guarantee the unicity of the created type. The first 3 characters could be a company prefix for example and the last field could be the UDF identifier.

How can I make persistent the type that I created when creating my UDF?

If you want to reuse the generated type in another CATIA session:

  • Save the CATGScript file in the Directory indicated in the Reference Directory for Types field (see Tools>Options>Parameters and Measure>Knowledge Environment tab)
  • check the Load extended language libraries check box and select the package containing the type you created.

What cannot be inserted into a UDF?

Please find below a list of features that cannot be inserted into a UDF:

  • Sub-elements.
  • Datums
  • Projections or intersections of a sketch (in your sketch if you want to insert it into a UDF) or the projected surface must be embedded into the UDF (but it is not recommended.)
  • Over-constrained sketches

Does the UDF keep link with the document that was used to create it?

No it does not.

What can I do with a User Feature with a PK1 license?

You can instantiate a UDF, modify its inputs, update it and integrate it in a Power Copy or in another UDF.

I've embedded my optimization into a UDF. It is launched by the VB action of a reaction, But it doesn't work at instantiation. Could you tell me why?

It is certainly because in the VB body of the action, the Optimization is accessed with its VB resolution and it is not referenced. When you instantiate the UDF, the path of the Optimization changes (it is aggregated under the UDF) and thus the action doesn't succeed anymore. To make it work, use a VBScript with an optimization argument in the action.

Can I use a Part that contains a UDF if I don't have KT1? How does the geometry behave?

Yes you can but there are restrictions. The feature is broken and you can only visualize/copy-paste it thanks to the backup-startup mechanism.

Can I insert non consecutive elements into a User Feature?

No. The components of a User Feature must be consecutive elements if they are located in an ordered set like an Ordered Geometrical Set. It is recommended to create the components of a template (PowerCopy or User Feature) in the same set and to select this set as the only component of the template.

What License do I need to:

  • Modify and update a part which includes a UDF but with no modification of the UDF Features: You don't need KT1 if you haven't modified anything that impacts the UDF (its direct inputs or some of the features.)
  • Modify the values of input parameters of a UDF: You need KT1 (in fact you could modify the input parameters through F(x) but you need KT1 to update the feature.)
  • Delete a UDF: You don't need KT1.
  • Move a UDF: KT1 is required.
  • Access the properties (attributes) of a UDF: You can access to numerical parameters (in F(x)). You can create a formula using those parameters. But the update will fail if you modify them without KT1.
  • Copy/paste a UDF: You can copy/paste as result or as result with link, you don't need KT1. If you want to copy/paste as spec, you need KT1 to update it.
  • Create a Power Copy containing a UDF: You can create a Power Copy including a User Feature without using the KT1 license.
  • Use a Power Copy that incorporates a UDF: You need KT1 to instantiate a Power Copy which incorporates a User Feature (because you need to update the User Feature.)