This dialog box enables you to manage correlation rules that automatically correlate dynamic values during code generation. You can:
- Add a new application
- Add a new rule
- Delete a rule
- Export rules
- Import rules
- Test a rule
Do one of the following:
|Relevant tasks||How to Correlate Scripts Using Design Studio|
User interface elements are described below (unlabeled elements are shown in angle brackets):
|<Application List >||
A list of applications and their rules.
|Add a new application to <Application List>.|
Enter a new rule for the selected application in Correlation Rules.
For details, see New Rule Pane.
|Delete the selected application or rule from the list.|
|Import a file containing correlation rule definitions.|
|Export a file containing a correlation rule definition.|
Test a correlation rule.
For details, see Token Substitution Testpad Dialog Box.
Enables you to define a new custom rule.
Record > Recording Options > Correlation > Rules > New Rule
This pane is available only for specific protocols. For a complete list of protocols and their associated nodes, see the Protocol Compatibility Table.
User interface elements are described below:
Opens the Advanced Correlation Properties Dialog Box.
Specify the type of action for the rule from the following options:
|Scan Type||The scan type: Regular Expression, Boundary Based, XPath query, or JSON query.|
|RegExp String||A regular expression to which this rule will apply. This element only applies to a Regular Expression scan type.|
The left-most boundary where the rule will apply. This element only applies to Boundary Based scan type.
The right-most boundary where the rule will apply. Use the drop-down menu to define this boundary as either the end of a string, a newline character, or a user-defined text. The element only applies to Boundary Based scan type.
|XPath query||An XPath expression to which this rule will apply. This element only applies to a XPath query scan type. When VuGen detects a value that matches this expression, it creates a web_reg_save_param_xpath function.|
|JSON query||A JSON query expression to which this rule will apply. This element only applies to a JSON query scan type. When VuGen detects a value that matches this expression, it creates a web_reg_save_param_json function. For details about creating a JSON query, see Internet resources on JSONPath expressions.|
Uses a prefix in all automatically generated parameters based on this rule. Prefixes prevent you from overwriting existing user parameters. In addition, prefixes allow you to recognize the parameter in your script. For example, in Siebel Web, one of the built-in rules searches for the Siebel_row_id prefix.
Matches the case when looking for boundaries.
|Use '#' for any digit||
Replaces all digits with a hash sign. The hash signs serve as wildcard, allowing you to find text strings with any digit.
Example: If you enable this option and specify HP### as the left boundary, HP193 and HP284 will be valid matches.
This element only applies to boundary based scan type.