XRule: Search Text
Use the Search Text rule to search for a specific string of text on the Page or PageComponent, but not inside the code.
For example, a search for the text string "AppScan® Enterprise Edition" would find it twice inside the following excerpt as highlighted:
<p> AppScan® Enterprise Edition does
not normalize the critical pages across or within jobs. This allows
an organization to define different criteria for Critical Pages across
its web properties, but still have them identified on a <a href="www.example.com/AppScan
Enterprise Edition/dashboard.asp"> AppScan® Enterprise Edition dashboard</a>.</p>However, the Search Text XRule would not find the third instance because it is inside code. To find "AppScan® Enterprise Edition" inside the page text and its code, use the Search Code XRule.
The text fields in the template XRules all accept regular expressions if they are preceded by regexp:. They do not accept DOS expressions.
| Page element | Description |
|---|---|
| Name | The name assigned to the XRule. |
| Description (optional) | Describe the purpose of the XRule so that you and other users can understand its purpose. For example, "Search for old product name in text" or "Search for profanity in text". |
| Search term (text or pattern) | Enter the text that must be found within the page content. Use plain text or a regular expression (prefix with regexp:). |
| Make the search case sensitive | Select this option if you want the search to be case sensitive. To find a match, the search criteria and the item found must be exactly the same. For example, if you entered www.example.com/Products/AppScan/ as a case-sensitive search, the XRule would not find www.example.com/products/Appscan. |
| PageComponent types to search | Select the type of PageComponent that should be searched for the term. For example, if you know that the term can only be found in PDF files, then choose that as the type. Limiting the document types that are searched reduces the time that the scan takes to search for the term. |
| Only enable XRule if it is required by a job or report | Select this option to have the XRule run only when required. If the XRule is not required by a job or report, it will not be run. Checking this option saves time when scanning your site because the XRule only runs when necessary. |
| Always enable XRule | Select this option to have the XRule run whenever the job runs. This method is the least efficient way to use an XRule. |
| Always disable XRule (if job experiences problems) | Select this option to disable the XRule from a job or report. The rule will never be run, even if it is required. Disable the XRule when it causes problems with the job, such as a scan continuing indefinitely. |
| This rule defines a privacy statement | Select this option when you want the pages that do not match this rule to be automatically reported in the Pages Collecting PII without a Privacy Statement Link report. |