When working in the IsoConfig.xml, filters are the last breakout in the tree view. While last on the list, these filters can have a profound impact on how items will behave.

Adjusting a filter could help sort an item in your BOM, remove the item from the BOM, allow the item to be given an annotation, set the layer of the component, etc.
One way to make filter creation easier is to look over the existing filters, so below I’ll document several of the out of the box filters and what function they serve:

Name=”Bend” Value=”Type = ‘Bend’”
Use the property Type to find an exact value.

Name=”Cross” Value=”Type LIKE ‘CROSS*’”
Use the property Type to find a value that starts with CROSS.
Notice that an exact match uses = while a search uses LIKE and includes an asterisk as a wildcard in the string.

Name=”Fastener” Value=”Type =’Gasket’ OR Type = ‘Bolt’ OR Type = ‘REINFORCEMENT-PAD’”
Using OR allows more than one condition to count as a match.

Name=”ElbowAndCompAtt1Sr” Value=”Type=’Elbow’ AND SHORTRADIUS=’SR’”
Using AND will require that both conditions are met.

Name=”ItemCodeNotNull” Value=”NOT [ITEM-CODE] IS NULL”
It may be easier to identify objects that do not meet the criteria you need, so using NOT can invert the results of your test. IS NULL means that the property is not filled out.

Name=”OletAndSkeyLascLaswOrLabw” Value=”Type = ‘olet’ AND (SKEY=’LASC’ OR SKEY=’LASW’ OR SKEY=’LABW’)”
Some properties are hard coded and mapped automatically. We have seen Type used in most of these filters, but another mapped property is SKEY. Some properties used in the out of the box filters are exclusive to specific object types, so it’s use may be limited.

If you want to map a property to be used in the IsoConfig.xml this can be done using the Iso.atr file.

Properties added in the BOM-ATTRIBUTES section can be used for filters and annotation. For more information on mapping properties to the Iso.atr see the article below:

Below is an example of how to use a custom property in a filter:
Name=”TestSupplier” Value=”Supplier = ‘Test’”

Depending on how a filter is going to be used you may need to use several of these strategies together.
Name=”OletAndSkeyLascLaswOrLabw” Value=”Type = ‘olet’ AND (SKEY=’LASC’ OR SKEY=’LASW’ OR SKEY=’LABW’)”

Notice this filter is using a combination of AND and OR statements with parenthesis to keep parts of the function split. The filter is finding Olets, but only the ones using SKEYs LASC, LASW, or LABW.

A rule of thumb for when building a filter is to aim for the result of your logical test to be true for the objects you want to work with.