Specifications

Server Behaviors 171
Note: It is important that the regular expression start and end with a slash (/). Otherwise it is used as a literal string
search. Regular expressions can be followed by the regular expression modifier
"i" to indicate case-
insensitivity (as in
/pattern/i). For example, VBScript is not case-sensitive, so it should use /pattern/i.
JavaScript is case-sensitive and should use
/pattern/.
Sometimes you might want to assign the entire contents of the limited search location to a
parameter. In that case, provide no pattern, as shown in the following example:
<searchPatterns whereToSearch="tag+OPTION">
<searchPattern>MY_OPTION_NAME</searchPattern>
<searchPattern paramNames="optionLabel" limitSearch="innerOnly">
</searchPattern>
</searchPatterns>
This sets parameter "optionLabel" to the entire innerHTML of an OPTION tag.
Attribute: paramNames
Description
A comma-separated list of parameter names whose values are being extracted. These are assigned
in the order of the subexpression. You can assign single parameters or use a comma-separated list
to assign multiple parameters. If other parenthetical expressions are used but do not indicate
parameters, extra commas can be used as placeholders in the Parameter Name list.
The parameter names should match the ones that are specified in the insertion text and the
update parameters.
Parent
searchPattern
Type
Attribute.
Required
Yes.
Values
paramName1, paramName2, ...
Each parameter name should be the exact name of a parameter that is used in the insertion text.
For example, if the insertion text contains
@@p1@@, you should define exactly one parameter
with that name:
<searchPattern paramNames="p1">patterns</searchPattern>
To extract multiple parameters using a single pattern, use a comma-separated list of parameter
names, in the order that the subexpressions appear in the pattern. Suppose the following example
shows your search pattern:
<searchPattern paramName="p1,,p2">/(\w+)_(BIG|SMALL)_(\w+)/¬
</searchPattern>
There are two parameters (with some text in between them) to extract. Given the text:
<%= a_BIG_b %>, the first subexpression in the search pattern matches "a", so p1="a". The
second subexpression is ignored (note the
,, in the paramName value). The third subexpression
will match
"b", so p2="b".