Custom Derived Output Support

These are the user defined or third party output files. The Integration supports the checkin of these types of derived outputs.

To use custom derived outputs, ensure the following:

  • Third Party file or user defined custom files must reside in the local working directory.
  • The Derived files should have the same name as the file it was created from.

    Example: For a TestPart.ipt, if the Custom Derived Output is of .zip format, the file name should be TestPart.ipt.zip.

  • Within the GCO the Customer should define the types using the postfix (Example: gli, .zip) as discussed further so that such files should be considered as Custom Derived Output.

All the derived outputs are checked in with separate formats of the same Derived Output Object or the CAD Type Object depending on the following settings:

  • If the MCADInteg-CreateDerivedOutoutObj flag in the GCO is set to TRUE, the derived outputs will be checked in the corresponding formats of the same Derived Output object linked to the CAD Model.
  • If the MCADInteg-CreateDerivedOutoutObj flag in the GCO is set to FALSE,the derived outputs will be checked in the corresponding formats of the same CAD Model object.

User can change the default settings for native derived outputs using the Preferences command.