Specifying end objects

To specify which object is the end object that is exposed in an asset, you must mark it in a Path element in the alias definition. The following example shows an existing alias alternate for populating a 2D asset:

Copy

<AliasAlternate name="2DGraphic">
  <Path>AssociatedAttachment:AssociatedAttachment[@role='contents']:@childRefs</Path>
        <Path>AssociatedAttachment:ConfiguredOccurreceGroup:@attachmentRef</Path>
<Path>ConfiguredOccurrenceGroup:*:@childRefs</Path>
        <Path>Occurrence:AssociatedAttachment:@associatedAttachmentRefs</Path>
   <Path>AssociatedAttachment:DataSet[@type='Image']:@attachmentRef</Path>
      <Path>DataSet:ExternalFile[@format='jpg' or @format='jpeg' or 
      @format='gif' or @format='bmp']:@memberRefs</Path>
      &FILE-ATTR;
</AliasAlternate>

To identify the end object, use the createRelation attribute on the last Path element:

Copy

<Path createRelation="VisAssetPopulatedByEndobj">

This causes the end object UID to be sent back through Lifecycle Visualization to the Teamcenter rich client, along with the createRelation identifier. The rich client then creates the VisAssetPopulatedByEndobj relation from the publishing page dataset to the end object.

To create two different relationships to the same end object, use this syntax:

Copy

<Path createRelation='VisAssetPopulatedByEndobj,AnotherVisRelationship'>

When customizing alias definitions, you can identify the end object for any asset and Teamcenter creates the relation specified. You can define your own custom relations and have them created too by adding appropriate createRelation clauses or by adding additional relation names to existing createRelation clauses.