Adding new Content-Based view rules
Instructions and examples of adding rules to define the site's logical structure.
Before you begin
- Logical Content Path (such as breadcrumbs)
- Custom (use regexps to define your own custom nodes)
Doing this enables AppScan® to display a logical application tree, instead of listing large parts of the site under a single node. When more than one rule is defined, AppScan attempts to match each URL to the rules in the order they are listed. As soon as it finds a match it includes the URL in the Content-Based tree following that rule and proceeds to the next URL.
Procedure
Example
Setting | Sample | Meaning |
---|---|---|
Content Path | <title>(.*?)</title> | All text between the title tags will be used as the basis for the node names. |
Separator | [:\->|] | These five characters will be treated as
separators. Therefore: <title>Home:Accounts</title> and <title>Home:Plans</title> will appear in the application tree as a parent node Home with two child nodes: Accounts and Plans |
Node Display Name | ^\s*(.*?)\s*$ | Spaces before and after the text will be removed when naming the node. |
Condition | Log out | Only pages containing the words "Log out" will be included in the application tree under this rule. |
Setting | Sample | Meaning |
---|---|---|
Node Location | /root/child/grandchild | All pages that fulfil the Condition are
added to the application tree under /root/child/grandchild Note: If the parent nodes in the specified branch do not exist, they
will be created. |
Condition | As this field is empty, all content to which the rule is applied will be added at this node location. Therefore, if this rule appears after the rule above, all pages that do not contain the words "Log out" will be added under the node /root/child/grandchild |