Propagating Information from an Existing Change Object
The propagate functionality is available for creating change requests, change notices, problem reports and variances. In the create window of these change objects, the Set Attributes step contains a Propagate information check box. When you select the check box, the following information is copied from the existing to the new change object:
• Complexity
• Name
|
|
The wt.change.propagateName property controls the propagation of the name attribute value of a change object. When set to true, the default, the name attribute value is propagated from an upstream change object or a template. Specify false to disable the propagation of the name attribute value. Only an administrator can configure this property.
|
• Description
• Need by date
• Affected objects
• Affected end items
• Attachments
The propagation functionality reduces the data entry to create the new change object.
The visibility of the Propagate information check box is controlled by the Change Information Propagation preference. Only an administrator can configure the preference settings.
When creating a change request from a change request or change notice, the Complexity list is not displayed by default. To enable the display of the Complexity list, an administrator should add the Complexity attribute in the Layouts tab of the Change Request type in the Type and Attribute Management utility. The complexity value is propagated to a new change request irrespective of the settings of the Propagate information check box. You can edit the complexity value, if required.
|
|
Administrators can customize the propagation logic by extending and registering the delegate ChangeItemComplexityDelegate.
|
To propagate the attachments from a change request to a change notice when using a change notice template, configure the wt.change.propagateAttachmentForCNTemplate.enabled property in the wt.properties file. The wt.properties file is located at <Windchill>\codebase\wt.properties. By default, the property is set to false. When set to true, the attachments are propagated from a change request to a change notice.
|
|
The remote change objects can be propagated to the Affected Objects table of a change request, problem report and variance. The local change objects can be propagated to all downstream change objects.
|
