Data Management Capabilities > Managing Part Structures > Windchill Options and Variants Capabilities > Filtering a Configurable Product Structure with the Option Filter > Standard and Alternate Option Filter > Customizing Filtering Behaviors for the Option Filtering Delegate > Configuring Standard and Alternate Behaviors > Standard Filtering Configuration File Example
Standard Filtering Configuration File Example
The out-of-the-box file for configuring the standard Option filtering behavior is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<FilterStrategy handler="com.ptc.windchill.option.filter.DefaultFilterStrategyHandler">
<FilterNode type="wt.option.ExpressionAssignable">
<ExpressionPolicy advanced="true" mode="STANDARD"/>
<FilterNode type="wt.option.ChoiceMappable">
<ExpressionPolicy advanced="false" mode="STANDARD"/>
Note that the Option filtering delegate provides customization hooks to help various types of customers (including PTC teams supporting other products such as MPMLink or Arbortext) define which navigation unit objects they consider filterable or supporting in the filtering process. The filtering expression policies will be applied after this determination is made to further restrict the set of objects for which basic or advanced expressions will be retrieved.
The policy above means that we shall extract choices for all ChoiceMappable objects. The customization hooks will narrow these objects down. For example, the Option teams has an additional requirement that the filterable implements a GenericizableUsageLink whose parent’s Genericizable has the type “generic”, etc. This type of restriction cannot be added to the configuration file because MPMLink does not have this condition. It is not possible to extract expressions for all expression assignable objects because the mode is STANDARD, the node is filtered out only when the expression on a filterable (e.g. WTPartUsageLink) or a supporting object (e.g. WTPart) evaluates to FALSE.