About 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 this feature user needs to note the following points:

  • 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.par, if the Custom Derived Output is of .zip format, the file name should be TestPart.par.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.