Wiki Page: Why is my Recording Rule not making the substitution correctly when employing conditions?

There are two known issues when using recording rules which have been addressed with the release of a patch for SilkPerformer 7.2 (SP72_Patch_02_ParsingRules) and this issue has been fixed in later versions. The known issues are as detailed below: A second Recording Rule is not applied if the first recording rule failed. Assume you have two rules (rule A and rule B) which can parse the same string, e.g. "New York", from two different, or the same, HTTP requests. When the string "New York" appears somewhere in the script, the recorder checks if this string should be replaced by a parsed value. This involves evaluating the "Conditions" in the "ScriptGen" section of rule A. If the conditions of rule A evaluate to "don"t replace", then the recorder fails to evaluate if rule B would mandate a replacement with a parsed value and therefore no substitution is made. If a possible rule hit occurs twice in the same sting, but the first occurrence does not meet the conditions then the recorder will not try to use the rule for the second occurrence of the value in the script. For example, the conditions of rule A are only evaluated for the first occurrence of "New York". If "New York" occurs multiple times in a string and the conditions prohibited a replacement for the first occurrence, no other occurrence is checked, although the conditions might evaluate differently for the later occurrences. If you require this patch please contact Support.