You can use wildcard characters (*) in report filters, but they are only allowed in filters that use the operators "==" or "!="; filters of any other type that contain "*" are in error, and you are prompted to re-type the filter. For example, you can use the wildcard in these filters:

The first filter would match the strings "part," "part1," "part_A," and "partabcdefg." The second filter would match the strings "my," "this_is_my_assembly," "autonomy," "not_yours," and "your".

If you add a backslash (\) in the right-hand side of a filter (after the operator), the system reads the character after the backslash literally (as itself), not as a special character. You can then filter for an asterisk character. For example, &asm.mbr.name>=part\* matches strings that are alphanumerically greater than or equal to the string "part*".

The system interprets backslashes in report parameters or between string quotes literally as backslash characters. It interprets the parameter "&asm.\mbr.name" as a report symbol named "asm.\mbr.name" (an invalid name), and the filter:

&asm.mbr.name=="match this\”

matches only the string "match this\”.

It treats a backslash that is not in a report parameter, not enclosed by string quotes, and not followed by another character as a null string (" "). It interprets anything between two string quotes literally; the filter:

&asm.mbr.name<":\\***"

matches strings that are alphanumerically smaller than ":\\***". For filters created prior to Release 11.0 that contain the wildcard character, the system interprets the character literally (as an asterisk).