Page Comparison

This setting overrides the pattern Genie uses to detect function key labels on screen when creating links/buttons for function keys.

...

pui["function key pattern2"] can be used along with pui["function key pattern"]. 

The pattern must be a regular expression with 4 capturing groups in this order:

...

The fourth capturing group only needs to match part of the description text. For example, if the text is "F13=Information Assistant" and the string "Information Assistant" is in a single output field, then the detector will see "Information Assistant" as the key description.

Example 1:

pui["function key pattern2"] = "(F|CA|CF|CK|CMD|CM) ?([0-9]{1,2}) ?([=:-]) ?(\\S+)";

...

Note that the pattern is matched on an entire row of 5250 characters, not just on a single output field. Unlike pui["function key pattern"], this pattern should not use the "^" and "$" meta-characters. 

Example 2:

The Example 1 pattern could match text incorrectly. For example, the text "OFF1:1" would not be function key, but the pattern would match. To avoid matching F, CA, CF, etc. that are on word endings, this pattern would work:

...

The pattern detects function key labels starting after a blank or starting at the beginning of a row–beginning with F, CA, CF, CK, CMD, or CM. Next is one or no spaces. Then 1 or 2 digits, followed by one or no spaces. Last are one or more non white-space characters. 

Where do you save this configuration option?  Here.

pui["function key pattern2"] is available with Profound UI Version 5, Fix Pack 4.0. 

pui["function key pattern2"] = /(F|CA|CF|CK|CMD|CM) ?([0-9]{1,2}) ?([=:-]) ?(\S+)/ig;

...