...
- To view config file match details, click the (+) icon at the left end of the row.
- To edit a config file match: hover the mouse over the Action icon for the element and choose Edit.
- To delete a config file match: hover the mouse over the Action icon for the element and choose Delete.
...
Note: When creating a rule to evaluate a block of config in a specified order, note that the “all of these lines in specified order” logic implies that each line is present and in that order, and there can be other lines in between. In this case the rule passes. If you do not want to allow other lines in between, use the “Contains This BLOCK” option. Also, in both the “Config File Must Contain” and “Config File May Not Contain” sections, each entered line is considered a regular expression to be matched against the configuration file. If you select one of the BLOCK options, the entire content of the field is considered a regular expression.
...
| Anchor |
|---|
| Using the Simple Rule Editor |
|---|
| Using the Simple Rule Editor |
|---|
|
Using the Simple Rule Edit
or
...
Note: You can move the bar between the Must Contain and May Not Contain panels to adjust the space available in each panel.
...
Note: When creating a rule to evaluate a block of config in a specified order, note that the “all of these lines in specified order” logic implies that each line is present and in that order, and there can be other lines in between. In this case the rule passes. If you do not want to allow other lines in between, use the “Contains This BLOCK” option. Also, in both the “Config File Must Contain” and “Config File May Not Contain” sections, each entered line is considered a regular expression to be matched against the configuration file. If you select one of the BLOCK options, the entire content of the field is considered a regular expression.
...
| Anchor |
|---|
| Using the CPD Editor |
|---|
| Using the CPD Editor |
|---|
|
Using the CPD Edit
or
...
