Report Filter Categories

The following table lists the filter categories that you can apply to your report data, including filter category descriptions and the categories’ property types—whether the filter category is a BOOLEAN, DATE, STRING, or STRING_LIST property.

See Report Filter Operator Symbols for information about which operators can be used with which Filter Property Types.

Report Filter Categories

Filter Category

Filter Property Type

Description

Feature

STRING

FEATURE name

Reserved User or Group

STRING_LIST

USER or GROUP that is RESERVEd in the vendor’s options file. This filter category can be used in the following ways:

• If no Reserved User or Group filter is applied, all features are used to report usage.
• If Reserved User or Group == <string> filter is applied, the <string> is treated as either a name of a user or a user group. Only features that have the specified user or user group named in its RESERVE list in the vendor daemon’s options file are used for reporting. All other features are filtered out.
• If Reserved User or Group =~ <string> filter is applied, the <string> is treated as a pattern of either a name of a user or a user group. The * character is treated as a wildcard. Only features that have the specified user or user group—that match the pattern—on its RESERVE list in the vendor daemon’s options file are used for reporting. All other features are filtered out.
• If Reserved User or Group != <string> filter is applied, the <string> is treated as either a name of a user or a user group. Only features that do not have the specified user or user group named on its RESERVE list in the vendor daemon’s options file are used for reporting. All other features are filtered out.
• If Reserved User or Group !~ <string> filter is applied, the <string> is treated as a pattern of either a name of a user or a user group. The * character is treated as a wildcard. Only features that have the user or user group —that match the pattern—on its RESERVE list in the vendor daemon’s options file that do not match the pattern are used for reporting. All other features are filtered out.

Included User or Group

STRING_LIST

USER or GROUP that is INCLUDEd in the vendor’s options file. This filter category can be used in the following ways:

• If no Included User or Group filter is applied, all features are used to report usage.
• If Included User or Group == <string> filter is applied, the <string> is treated as either a name of a user or a user group. Only features that have the specified user or user group named in its INCLUDE list in the vendor daemon’s options file are used for reporting. All other features are filtered out.
• If Included User or Group =~ <string> filter is applied, the <string> is treated as a pattern of either a name of a user or a user group. The * character is treated as a wildcard. Only features that have the specified user or user group—that match the pattern—on its INCLUDE list in the vendor daemon’s options file are used for reporting. All other features are filtered out.
• If Included User or Group != <string> filter is applied, the <string> is treated as either a name of a user or a user group. Only features that do not have the specified user or user group named on its INCLUDE list in the vendor daemon’s options file are used for reporting. All other features are filtered out.
• If Included User or Group !~ <string> filter is applied, the <string> is treated as a pattern of either a name of a user or a user group. The * character is treated as a wildcard. Only features that have the user or user group —that match the pattern—on its INCLUDE list in the vendor daemon’s options file that do not match the pattern are used for reporting. All other features are filtered out.

License Key

STRING

License key on FEATURE or INCREMENT line

Version

STRING

Version on FEATURE or INCREMENT line

Vendor String

STRING

VENDOR_STRING=text on FEATURE or INCREMENT line

Hostid on Feature Line

STRING

HOSTID on FEATURE or INCREMENT line

Distributor Information

STRING

dist_info=text on FEATURE or INCREMENT line

User Information

STRING

user_info=text on FEATURE or INCREMENT line

Asset Information

STRING

asset_info=text on FEATURE or INCREMENT line

Issuer

STRING

ISSUER=text on FEATURE or INCREMENT line

Notice

STRING

NOTICE=text on FEATURE or INCREMENT line

Expiration Date

DATE

Expiration date (in the format dd-mmm-yyyy) for a feature as specified on the FEATURE or INCREMENT line (string with wildcards) in the license file.

To create an Expiration Date filter condition, use the date format mm/dd/yyyy in the Event Filter field. For example, 04/19/2016 and 4/19/2016 are valid values for the date 19-apr-2016.

Note:The specified year must be four digits in length.

Expiration dates can also be specified as permanent in the license file, which means that the feature never expires. Permanent features have their expiration dates stored as NULL in the database.

Because expiration dates are always either a date or the literal permanent, the NULL value in the database is never overloaded to mean “not defined.” (Expiration dates are always considered to be “defined.”)

Using the Expiration Date filter category, you can filter features that have a permanent expiration date by constructing a filter condition using the keyword permanent. For example, if you create the filter condition Expiration Date == permanent, the filter will pick up all features whose expiration date is permanent in the license file.

The following rules apply when using the keyword permanent as a value for an Expiration Date filter condition:

• It is valid only as a keyword for the Expiration Date filter category. When used with any other filter category, it is treated as a string.
• It is case insensitive.
• Only the == and != operators are valid for use with permanent.

Serial Number (SN)

STRING

SN=nnn on FEATURE or INCREMENT line

Issued

DATE

ISSUED=dd-mmm-yyyy on the FEATURE or INCREMENT line.

This is the date that the feature was issued, as specified in the license file.

To create an Issued filter condition, use the date format mm/dd/yyyy in the Event Filter field. For example, 04/19/2016 and 4/19/2016 are valid values for the date 19-apr-2016.

Note:The specified year must be four digits in length.

The issued date may not have been specified in the license file, in which case the data is NULL in the database. Features that have no issued date specified cannot be filtered by issue date.

Suite Package

BOOLEAN

The Suite Package filter works in the following ways:

• If no Suite Package filter is applied, all features are used to report usage.
• If Package Component == Y or N (both Y and N behave the same way), only features that are packages that are suites are reported on. All others (package components themselves and features outside of packages) are filtered out.
• If Package Component != Y or N (both Y and N behave the same way), features that are packages that are suites are filtered out. All others (package components themselves and features outside of packages) are reported on.

Important:Using other filter operator symbols will not result in a valid filter.

Package Component

BOOLEAN

The Package Component filter works in the following ways:

• If no Package Component filter is applied, all features are used to report usage.
• If Package Component == Y or N (both Y and N behave the same way), only package component features are reported on. All others (packages themselves and features outside of packages) are filtered out.
• If Package Component != Y or N (both Y and N behave the same way), only package component features are filtered out. All others (packages themselves and features outside of packages) are reported on.

Using other filter operator symbols will not result in a valid filter.

User

STRING

User name

User IP Address

STRING

User IP address (nnn.nnn.nnn.nnn)

User Platform

STRING

Platform on which the application was compiled to run

User Display Name

STRING

User display name (UNIX only)

User Project

STRING

Use LM_PROJECT environment variable (or Windows registry)

FlexNet Licensing Version

STRING

Product’s FlexNet Publisher licensing version

User Host Name

STRING

User host name

User Product Version

STRING

Version of product actually used

Checkout Data

STRING

Value of CHECKOUT_DATA passed by the application to the license server when the license is checked out

Group

STRING_LIST

GROUP name in end-user options file for vendor

Host Group

STRING_LIST

HOST_GROUP name in end-user options file for vendor

See Also

Classic Reporting

Report Configuration Pages

Report Filter Operator Symbols

Running Classic Reports