Arbortext IsoDraw > Extensions > BOM XML Reference > BOM XMLFile Description > <instance>
  
<instance>
The <instance> element is a child of <occurrence>. Each <instance> element in the BOM XML file corresponds to a graphic object referenced by one or more callouts in the illustration. (Graphic objects with no callouts have no <instance> element in the BOM XML file.) Attributes of the <instance> element contain the object information for the graphic object.
If one callout references multiple graphic objects in the illustration, in the BOM XML file, the <occurrence> element for that callout <item> will contain multiple <instance> elements. However, within a single <occurrence>, all child <instance> elements must be unique. (See Example A.)
If multiple callouts reference the same graphic object in the illustration, the <instance> element for that object appears in multiple <occurrence> elements in the BOM XML file. (See Example B.)
<instance> Syntax
<instance isoId="ID" isoName="Name" isoTip="Tip"/>
<instance> Attributes
Description
isoID
The object ID for the graphic object in the illustration. The isoID attribute value must match the value of the ID field in the Object info dialog box.
isoName
The object name for the graphic object in the illustration.
When you export an illustration to a BOM-formatted Object List, the isoName attribute value gets the value of the Name field in the Object info dialog. However, when you update the illustration from a BOM XML file, the isoName value is ignored. It cannot be used to update the Name value in the illustration.
isoTip
The object tip (hover tooltip) for the graphic object in the illustration.
When you export an illustration to a BOM-formatted Object List, the isoTip attribute value gets the value of the Object tip field in the Object info dialog. However, when you update the illustration from a BOM XML file, the isoTip value is ignored. It cannot be used to update the Object tip value in the illustration.
<instance> Elements
Description
n/a
<instance> has no child elements.
<instance> Example A: One Callout References Multiple Objects
In the illustration, the callout F00.SFTY-SET references two graphic objects, as a set. In the BOM XML file, the <instance> elements for AUTOID_1412:CIRCLE_CLIP and AUTOID_1366:SAFETY_WASHER are both children of a single <occurrence> element for the callout <item> F00.SFTY-SET.
<item calloutValue="F00.SFTY-SET">
<occurrence>
<instance isoId="AUTOID_1412" isoName="CIRCLE_CLIP"/>
<instance isoId="AUTOID_1366" isoName="SAFETY_WASHER"/>
</occurrence>
</item>
<instance> Example B: One Object Referenced by Multiple Callouts
In the illustration, the callouts Z43.RING-SFTY and Z49-ALT.RING-SFTY both occur once, and they both reference the same graphic object AUTOID_1379:SAFETY_RING. In the BOM XML file, the <instance> elements for CIRCLE_CLIP and SAFETY_WASHER are both children of a single <occurrence> element for the callout <item>F00.SFTY-SET.
<item calloutValue="Z43.RING-SFTY">
<occurrence>
<instance isoId="AUTOID_1379" isoName="SAFETY_RING"
isoTip="Click for safety ring specifications. Alt. available."/>
</occurrence>
</item>
<item calloutValue="Z49-ALT.RING-SFTY">
<occurrence>
<instance isoId="AUTOID_1379" isoName="SAFETY_RING"
isoTip="Click for safety ring specifications. Alt. available."/>
</occurrence>
</item>