How to use wildcards to create filters?

  • KB ID: 1000284

  • Added: 19-05-2010

  • Last updated: 03-03-2011

View products that this article applies to.
Outpost Network Security 2.0
Outpost Antivirus Pro 2009
Outpost Antivirus Pro 7.0 - 7.6
Outpost Antivirus Pro 8.0
Outpost Antivirus Pro 8.1
Outpost Antivirus Pro 8.1.1
Outpost Antivirus Pro 8.1.2
Outpost Antivirus Pro 9.0
Outpost Antivirus Pro 9.1
Outpost Firewall Pro 8.1
Outpost Firewall Pro 8.0
Outpost Firewall Pro 2008
Outpost Firewall Pro 2009
Outpost Firewall Pro 7.0 - 7.6
Outpost Firewall Pro 8.1.1
Outpost Firewall Pro 8.1.2
Outpost Firewall Pro 9.0
Outpost Firewall Pro 9.1
Outpost Security Suite Pro 8.0
Outpost Security Suite Pro 8.1
Outpost Security Suite Pro 2007
Outpost Security Suite Pro 2008
Outpost Security Suite Pro 2009
Outpost Security Suite Pro 7.0 - 7.6
Outpost Security Suite Pro 8.1.1
Outpost Security Suite Pro 8.1.2
Outpost Security Suite Pro 9.0
Outpost Security Suite Pro 9.1
Outpost Security Suite Free

A wildcard is a character that can be used as a substitute for any of a class of characters in a filtering parameter, thereby increasing the flexibility of filtering.

In filtering parameters, you can use the following metacharacters:

  • Asterisk ( * ) - Matches any string of characters. It can represent zero characters, all single characters or any number of any characters.

    You can, for example, display all files with the extension "exe" and only them by typing "*.exe" in Include parameter (such filter will not display files with the extension "exec").

    "svc*" matches files which are prefixed with "svc" such as svchost.exe but scsvc.exe or test.svc will not be displayed.
  • Question mark ( ? ) - Matches any single character (exactly one character). Thus, two question marks in succession would represent any two characters in succession, and three question marks in succession would represent any string consisting of three characters.

    For example, "app??.exe" matches app34.exe and appex.exe files.

This material provides me with the information I need:


Didn’t find a solution? Contact us!

If you couldn’t find an answer here, contact Agnitum’s technical support engineers for assistance. We’ll get back to you within one business day.

Contact technical support engineers for help