Advanced Customization > Business Logic Customization > Customizing Change Management > Mass Change Operations > Customization Points
  
Customization Points
Adding and Extending Operations
The mass change client supports the ability to add new or extend existing operations to the client. The javadoc in the class MassChangeFilterDelegate has detailed instructions on how to do this.
While the filter delegate handles the processing of the mass change operation, not all operations are applicable for the selected object types. (For example a WTDocument is not valid for mass change operations handling part usage links.) In order to indicate which operations are supported for the selected objects validation is required. See the Mass Change – Supported Types best practice for details.
Extending Document Specific Operations
When processing the document operations Insert existing document or Remove related document there is a delegate that is used based on the relationship selected and the selected objects for the mass change. New delegates can be implemented to process relationships and/or selected objects. Currently the document relationships supported are Described By and Referenced By for Documents and Passive for CAD Documents. See javadoc in the AssociationDelegate and implementing classes for more details on the implementation and configuration.
Support Parts Built from CAD
Starting in the Windchill 10.2 M030 release, the mass change operation will support changes to parts built from CAD documents (i.e., parts with an active “owner” relationships to CAD documents). When Parts Built from CAD support is enabled the mass change behavior will be as follows:
The mass change operation will expose a publish action to apply the part changes to the backing CAD object.
The preview table will show a different set of actions (e.g., Include, Exclude, and Export to file).
The preview table will show all selected target objects, including ineligible ones.
A new "Exclusion Reason" column is displayed to explain why an object was ineligible, as well as a strikethrough on the ineligible object.
The mass change action is removed from the change task wizard, but it remains on the resulting objects table of the change task information page.
For compatibility with prior Windchill releases CAD support will not be enabled by default. To enable Parts Built from CAD support the following property should be set in the site.xconf file : massChange.enableCADSupport=true
* 
A future Windchill release will make support of Parts Built from CAD mandatory, and the above property will be removed.
Customization Updates
Installations with customized mass change code will need to update that code to be compatible with changes described in the “Support Parts Built fro,m CAD” section.. The following methods and in package com.ptc.windchill.enterprise.massChange.filters have been deprecated and will be removed in a future Windchill release:
MassChangeFilterDelegate.evaluate(Map<Changeable2, String> result, String action, List<Changeable2> selectedItems)
MassChangeFilterDelegate.processOperation(List<Changeable2> nonExcludedItems)
AbstractDefaultFilterDelegate,massChangeOperation()
AbstractWorkableFilterDelegate.doOperation(Changeable2 source_changeable, WTCollection target_changeables)
AbstractWorkableFilterDelegate.processExclusionCriteria(WTCollection targets, Changeable2 sourcePart)
AbstractPartUsageFilterDelegate.validateForQuantityUnit()
All extended classes with methods that override those listed above are also deprecated. See the JavaDoc of the deprecated methods for information on replacements.