A relationship "INV Attachment", similar to "Derived Output" relationship
installed by X-CAD Design Management, is installed by the Inventor App
Server installation.
By default, the connector creates a derived
object and saves it as a separate object for the generated CAD file.
- If the value of this attribute is FALSE, then no separate object is
created in ENOVIA for the attachment file. Instead, the file is checked
into the same business object as the model file and in the same format.
So in case there is a linked attachment Doc file "test.doc" with an Inventor
part file "test.ipt" then both these files will be checked into the "prt"
format of the object of type "INV Component"
representing the Inventor part.
- If the value of this attribute is TRUE, then a separate object of
type "INV Attachment" is created in ENOVIA for the attachment file. In
ENOVIA, this attachment object is connected to the business object representing
the model file, with the "INV Attachment" relationship. So in case there
is a linked attachment Doc file "test.doc" with a Inventor part file
"test.ipt" then,
- An object of type "INV Attachment" is created.
- The "test.doc" file is checked into the OBJ format of this object.
- The attachment object is connected to the CAD Model object of type
"INV Component" representing the Inventor
part "test.ipt", with the "INV Attachment" relationship.
Note that OOTB the "MCADInteg-TypeFormatMapping" in the GCO has the
following entries for attachment type:
attachment|INV Presentation,drw
attachment|INV Drawing,drw
attachment|INV Component,prt
attachment|INV Assembly,asm
attachment|INV Attachment,OBJ