You can specify ObjectTypes as part of the rule criteria in several of the rule types. See the Classification TopNodes node in MetaDataBrowser to find the string to use with the ObjectTypes attribute, as highlighted in the illustration below.
-
You must provide the value from the UserName field.
-
Only use exact ObjectTypes such as piping components. The software does not honor higher level BOC nodes such as Piping.
You can use the asterisk [*] as a wild card character. For example, type Piping* to include Piping Components, Piping Specialty Items, Piping Instruments, Piping Welds, and so forth in the rule.
When the software processes an object, the ObjectType is written to the CodelessIFCRule log file. You can refer to this log file to determine which ObjectType to use. Two example log entries are shown below:
Example 1
@2/3/2015 4:54:13 PM - ProcessObject ? [Piping Components] - 'Flange-0403'
Example 2
@10/28/2014 12:44:10 AM - CreateInterference ? - [Slab] - 'Slab-0101' & [Member Part Linear] - 'MemberPart-0202'
You can simplify post-processing rules that support LimitToObjectTypes1 and LimitToObjectTypes2 if LimitToObjectTypes1 and LimitToObjectTypes2 have identical values. The simplified rule is LimitToObjectTypes. You can also simplify post-processing rules that support both ExcludeObjectTypes1 and ExcludeObjectTypes2 using ExcludeObjectTypes.
Several of the rules support wild cards for other rule criteria attributes. See Advanced String Comparisons Using the Like Operator in the tutorial available at http://www.vb6.us/tutorials/conditional-expressions-visual-basic-tutorial.