Administration > Change Tracking Administration > Change Tracking XML Configuration
  
Change Tracking XML Configuration
The changeTracking.xml configuration file allows you to configure which change events and change event details are tracked. This file is located at <Windchill>/codebase/changeTracking/changeTracking.xml.
The table below outlines the various tags you can insert within the change definition element.
* 
Do not include spaces in values assigned to tags.
Tag
Description
<classname>
Specifies the target class name. Must be the same target class as defined in the lcs.plugins.properties file.
<processor>
Specifies the processor used for the change event logic when any of the change events for the target object occur.
<types>
Contains multiple <type> elements.
<type>
Contained within the <types> element. Contains the specific type names.
<typename>
Contained within the <type> element. Specifies which PTC FlexPLM object type the change definition applies to; you can configure the system to track different changes for different subtypes of the same target object. If you are only using one <type> element for the target class, set it to the root type. All subtypes inherit this configuration unless you override the root Type settings for a given subtype. If you set an attribute on a subtype, it is only available to that subtype and changes are not tracked at the root level for that type.
<events>
Might contain multiple elements. Events are defined per type; event names, tracking designation, and tracked attributes are for the given type specified in the <type> element.
<eventName>
Contained within the <events> element. Identifies which change events are tracked for the target object. Out-of-the-box, PTC FlexPLM supports five events:
• CREATE
• UPDATE
• CHECKIN (for select iterated objects)
• DELETE
• CHANGESTATE
<tracked>
Contained within the <events> element. Indicates whether the given event specified by the <eventName> element is tracked or not. This element supports two values:
• true (event is tracked)
• false (event is not tracked)
<content>
Contained within the <events> element. Indicates whether or not the content of an image page is tracked or not. This element supports two values:
• true (adding and removing content is tracked)
• false (adding and removing content is not tracked)
* 
This element applies to image pages only. You are not required to enter this element if you are defining change tracking for objects other than image pages.
<attributes>
Contained within the <events> element. Specifies those attributes whose values are tracked along with the given event specified by the <eventName>. Multiple attributes must be comma separated; if you do not need to track attributes for a given event, enter a single space between the <attributes> and </attributes> tags.
* 
The CHANGESTATE and DELETE events do not support attribute tracking; omit the <attributes> element when defining these events.
The example below tells the system to track the following for the Product type and the Product/Apparel subtype:
• Update change events
• The product name and product number attributes when updates are made
• Changes to the lifecycle state
<changeDefinition>
<classname>com.lcs.wc.product.LCSProduct</classname>
<processor>com.lcs.wc.product.ProductChangeAuditProcessor</processor>
<types>
<type>
<typename>Product</typename>
<events>
<event>
<eventName>CREATE</eventName>
<tracked>false</tracked>
<attributes> </attributes>
</event>
<event>
<eventName>UPDATE</eventName>
<tracked>true</tracked>
<attributes>productName,productNumber</attributes>
</event>
<event>
<eventName>DELETE</eventName>
<tracked>false</tracked>
</event>
<event>
<eventName>CHANGESTATE</eventName>
<tracked>true</tracked>
<event>
</events>
</type>
<type>
<typename>Product\Apparel</typename>
<events>
<event>
<eventName>CREATE</eventName>
<tracked>false</tracked>
<attributes />
</event>
<event>
  <eventName>UPDATE</eventName>
<tracked>true</tracked>
<attributes>Apparel_Test</attributes>
</event>
<event>
<eventName>DELETE</eventName>
<tracked>false</tracked>
</event>
<event>
<eventName>CHANGESTATE</eventName>
<tracked>true</tracked>
</event>
</events>
</type>
</types>
</changeDefinition>