The connection between Windchill™ Containers (Products and Libraries) and one or more IBM Rational Team Concert Project Areas are stored within an additional Windchill attribute of the Product or Library instance. Therefore the Windchill schema is altered.
Likewise, links from Windchill ChangeRequests to RTC Work Items are stored into an attribute of each ChangeRequest instance.
The type for these additional Windchill Product and ChangeRequest attributes is defined using a new Windchill Global Attribute. (Windchill’s global attributes can easily be added to the Windchill schema of various resources).
Note that as you perform these steps, some Windchill pages use Java applets. Make sure to review the tips in the Configuring Java Settings section to successfully follow the procedures. As of Windchill 11, these Windchill Java applets are fewer in appearance yet a few do still remain.
The process steps are:
[ * ] Important: It is mandatory that the Internal name chosen here matches the value you enter in the Servlet Manager’s context property oslc-windchill.windchill.attribute.product.relatedResource. See Configuring the Windchill adapter properties for more details.
The Product Screen for a new Product within the Windchill web application as seen in a typical browser window.
Figure: Windchill’s OSLC Resource Manage Attributes Screen
The Product and Attribute Screen for a new constraint within the Windchill web application as seen in a typical browser window.
Figure: Windchill’s Attributes Screen Constraints
The Windchill Adapter provides extensions to Windchill enabling the display of OSLC links to ALM Project Areas and ALM Work Items within the forms of the PLM system. The Adapter extends Windchill’s data schema and introduces appropriate user interface custom widgets for the new data attributes. Therefore the underlying information stored in the created attribute should be hidden to the end user, as the default display would be irrelevant.
Attribute visibility can currently be set for the Create New and Edit operations.
One can view and set the visibility for the attribute for a particular operation. If an attribute is inherited from a parent type, its visibility can only be made more restrictive than the attribute visibility on the parent type; it cannot be made less restrictive. Changes made are immediately reflected in the Visibility by Operation view of the type information page Attributes tab.
To hide the created attribute in end user views, use the following procedure:
[ * ] Important: It is mandatory that the Internal name chosen here matches the value you enter in the Servlet Manager’s context property oslc-windchill.windchill.attribute.changeRequest.relatedResource. See Configuring the Windchill adapter properties for more details.
Follow the steps performed for the Product attribute to finalize the Change Request attribute creation as described in the previous sections: Modifying the constraints and Hiding the attribute.