Integration with Other Applications > Integration with Cadence Allegro Design Workbench > Library Setup and Maintenance > Windchill Attribute Setup
  
Windchill Attribute Setup
As soon as synchronization is done, every Allegro Design Workbench Library part (LPPart) must have a corresponding Windchill part (WTPart). Library and Windchill part attributes (parameters) are the objects for synchronization.
* 
In an Allegro Design Workbench Library, only String and Real Number attributes are supported, but in Windchill, attributes must be of type String.
The Allegro Design Workbench parts have specific attributes that must be synchronized with corresponding Windchill part attributes. For example, we have the following Allegro Design Workbench “ECAD Component” specific attribute set with values:
<Attribute name="CLASS" value="I/O" />
<Attribute name="DESCRIPTION" value="Header 2x2 Dual Row" />
<Attribute name="MFG" value="10-6634M436" />
<Attribute name="MFG_PN" value="10-6011ba9874B3M182456" />
<Attribute name="PACK_TYPE" value="10-66MM3M" />
<Attribute name="PART_TYPE" value="HEADER" />
<Attribute name="PTF_SUBTYPE" value="10-666cba9874B3M182456" />
All library parts have an important attribute that represents the part classification. It is presented in the following format:
<Impl_Interface name=" CAD Component Classification.Headers [v1.0] ">
To integrate Windchill with Allegro Design Workbench Library, we must add the same set of global attributes to a specific Windchill part subtype (business object type) that is described next. To keep information about the part’s classification, a global attribute with the name Library Part Classification (internal name LPClassification) is added to the corresponding WTPart subtype by the ADW Gateway Server side installer.
In an Allegro Design Workbench Library, the part name is a concatenation of the part number and the part master ID, separated by a colon (for example, name="664438-001:1245739558002"). However, in Windchill, the new WTPart created as a result of Allegro Design Workbench -to-Windchill synchronization, has a name the same as the library part description (or library part number if description is empty). In order to retain information about the library part master id value, a global attribute with name Library Part Oid (internal name LPMasterOid) is added to the corresponding WTPart subtype by the ADW Gateway Server side installer. Global attributes in Windchill are instances of a reusable attribute definition that are added to a type or subtype.
For more information, see Managing Reusable Attributes.
* 
The values of ‘LPClassification’ and ‘LPMasterOid’ global attributes MUST not be changed by the user during the WTPart lifecycle.
* 
If a part is created in Windchill and the LPClassification attribute value is not defined, the corresponding ADW Part created in the ADW Library has a default classification of CAD Component Classification.UnClassified [v1.0]
* 
WindchillInfo*Engine has two reserved names: ‘class’ and ‘obid’ (both in lower and upper cases) that must not be used as global attribute names. To manage Allegro Design Workbench‘class’ and ‘obid’ information in Windchill, these library attributes must be mapped to different names. If these attribute names are not mapped, they are skipped on the Adapter level to prevent an Info*Engine error.
To create a new reusable attribute which can be added to subtypes as a global attribute, use the following procedure.
1. Log in to Windchill as the Windchill site administrator.
2. Navigate to Site > Utilities.
3. Click Type and Attribute Management.
4. Select Manage Reusable Attributes in the navigation pane.
5. Create a new attribute organizer. For example, you can use ECAD_ATTRIBUTES, or any other name.
6. Create a new reusable attribute with a String data type under this attribute organizer. For example “MFG_PN”.
7. Create a new reusable attribute with a String data type for each of the named Allegro Design Workbench “ECAD Component” specific attributes.
* 
All Windchill reusable attributes must have a Logical Identifier, which for synchronization purposes must be equal to the attribute Internal Name. If the Logical Identifier is not defined, the integration tasks cannot be performed.