| Verification Filter Defaults (tlvsc2110m000) |  |
| use.session.to define the settings for verification filters, and to link verification filters to verification codes. Per verification code you can define one generic verification filter, and one or more specific verification filters. Generic verification filter The generic filter defines the checks that are executed to verify all software components in all packages. Depending on the filter settings, the checks in the generic filter can generate two types of warnings: "Filtered to Handle" warnings. You must handle these warnings immediately. You must either solve or accept these filtered warnings. "Non-filtered" warnings that you do not have to handle immediately. Note The generic filter that is generated during the installation of VSC generates only "Filtered to Handle" warnings. Specific verification filters Specific filters are used to reduce the number of "FiItered to Handle" warnings for a specific package, module or VRC. Each specific filter is derived from the generic filter, and therefore executes exactly the same checks as the generic filter. In a specific filter, you can indicate for each check whether you want to generate "FiItered to Handle" warnings or "Non-filtered" warnings. Note: you cannot disable checks, or add extra checks in a specific filter. If you select a check, which is not present in the generic filter, VSC ignores this check. To define the verification filter properties The session contains various tabs, such as Filter, Sessions, Scripts, and Domains, where you must specify the filter properties. Filter tab In the Filter tab, you must specify the basic filter settings, such as the priority filters and the category filters. The priority filters determine: The type of warnings ("FiItered to Handle" or "Non-filtered") that VSC must generate for the various error types. Whether these warnings can be accepted, or must be blocked. The category filters determine the type of warnings ("FiItered to Handle" or "Non-filtered") that VSC must generate for the various categories of checks ("General" checks, "Tools Consistency" checks , "Application Logic" checks, and so on). For specific filters, you must specify the package, module or VRC to which the filter applies. Component related tabs The remaining tabs in this session relate to the different types of software components, such as sessions, tables, and scripts. Use these tabs to specify the checks that must be performed for each type of component. For example: For forms, you can perform checks on standard options, specific options, buttons, various form field options, and so on. For tables, you can perform checks on table fields, indices, reference fields, messages, and so on. For scripts, you can perform checks on functions, where used, return values, and so on. Note: In the Scripts tab, you can enable one or more source analyze codes for the verification filter. Source Analyze Codes perform user-defined checks on scripts such as UI scripts, DLLs and DALs. Each Source Analyze Code is linked to a search pattern that consists of start expressions, end expressions and search expressions. For more information, refer to Source Analyze Codes. Check boxes in the component related tabs Important! The meaning of the check boxes in the component related tabs depends on the type of verification filter. In the properties of the generic filter, the check boxes indicate which checks are executed when you run VSC: When you select a check box, VSC executes the corresponding check. When you clear a check box, VSC ignores the corresponding check. A specific filter executes exactly the same checks as the generic filter. When you create a specific filter, VSC automatically selects the appropriate check boxes, according to the selection in the generic filter. In the properties of a specific filter, you can use these check boxes to determine the type of warnings that VSC will generate. You cannot use the check boxes to enable or disable checks: When you select a check box, which is also selected in the generic filter, VSC executes the check. The resulting warnings are stored as "FiItered to Handle". When you clear a check box, which is selected in the generic filter, VSC still executes the check, but generates "Non-filtered" warnings. When you select a check box, which is not selected in the generic filter, VSC does not execute the check.
Fields | Description
Analyze Codes | If this check box is selected, VSC executes all source analyze codes, which are enabled for the verification filter. If this check box is cleared, VSC ignores the analyze codes. To enable source analyze codes for the filter, click the Analyze Codes button. The Source Analyze Codes per Verification Filter (tlvsc2512m000) session starts, where you can select the desired source analyze codes. For more information, refer to Source Analyze Codes.
Filter
Verification Code | The verification code to which the filter is linked.
Package | The package for which the (specific) filter is defined. For the generic filter, this field must be empty.
Module | The module for which the (specific) filter is defined. For the generic filter, this field must be empty.
Package VRC (Version) | The version of the package for which the (specific) filter is defined. For the generic filter, this field must be empty.
Package VRC (Release) | The release of the package for which the (specific) filter is defined. For the generic filter, this field must be empty.
Package VRC (Customer) | The customer extension of the package VRC for which the (specific) filter is defined. For the generic filter, this field must be empty.
Run VSC before check in | If this check box is selected, VSC automatically starts, when an engineer checks in a software component. If this check box is cleared, the engineer must run VSC manually to verify the component. For details, refer to To run VSC.
Priority Filter
High / Normal / Suspicious / Low | If this check box is selected, VSC generates "FiItered to Handle" warnings for errors with the selected priority. You must handle these warnings immediately. If this check box is cleared, VSC generates "Non-filtered" warnings for these errors. You do not have to handle these warnings immediately.
Accept | If this check box is selected, you can accept the warnings that VSC generates for errors with the selected priority. If this check box is cleared, you cannot accept these warnings, but you must solve them. For more information, refer to To handle warnings.
Block | If this check box is selected, warnings that are generated for errors with the selected priority can block the check-in of software components. If a blocking error occurs, you must accept the corresponding warning before you can continue the check-in of the involved software component. If you do not accept the warning, you must solve the problem and run VSC again, before you can check-in the component. If this check box is cleared, the warnings that are generated for errors with the selected priority do not block the check-in process.
Category Filter
General | If this check box is selected, VSC generates "FiItered to Handle" warnings for the checks of this category. You must handle these warnings immediately. If this check box is cleared, VSC generates "Non-filtered" warnings for this category. You do not have to handle these warnings immediately.
Commands | Description
Analyze Codes | This command starts the Source Analyze Codes per Verification Filter (tlvsc2512m000) session, where you can enable one or more source analyze codes for the verification filter. For more information, refer to Source Analyze Codes. To make sure that VSC executes the enabled source analyze codes you must select the Analyze Codes check box.