Ad Hoc Instance Based Attributes
Windchill PDMLink allows you to add attributes to modeled classes like wt.part.WTPart without changing the model. You can do this using the Windchill Type Manager. See the Windchill Business Administrator's Guide for details. If you extend a modeled class by creating a soft type or add an attribute to a modeled class, Windchill ESI services obtain the added attribute when the target (that the object is released to) uses an appropriately modified version of the ESI response meta information file as described in the previous section of this document.
Windchill PDMLink also allows you to add instance based attributes (IBAs) to a modeled class that is an IBAHolder, such as wt.part.WTPart without using the Windchill Type Manager.
IBAs added in this way are called ad hoc attributes.
See the Windchill Application Developer’s Guide for details about IBAHolder objects.
If you wish to publish the attributes that are added to a wt.part.WTPart object by any of the above described means, you must
1. Create an appropriately modified version of the ESI response meta information file, and
2. Edit the relevant distribution target (or create a new one) to point to the modified version of the file.
Releasing the part to the thus edited (or created) target would result in the added attributes of the part being sent with the ESI response.
* 
Make sure you follow the procedure described in Procedure while modifying the contents of the ESI response meta information file.
* 
Changing the contents of the response meta information file (to cater to the added attributes) can change the structure of the ESI response.
Was this helpful?