Megger Baker AWA-IV User Manual page 161

Refer to https://msdn.microsoft.com/en-us/library/bb982727.aspx for more explanation about
regular expression syntax. Note that the ECMAScript variant is being used here. Regular expressions are very
powerful, but can prove tricky to get right. Users already familiar with modern regular expression syntaxes—even
those influenced by Perl—should still refer to the official description because ECMAScript (that is, standardized
JavaScript) regular expressions sometimes deviate in meaning from other variants of Perl-inspired regular expressions.
AppliesTo (optional)—Provides a set of AWA user interface contexts to which the related field specification should be
applied. The values listed can be separated by commas, spaces, or vertical bars. They are essentially added together
in a set. The individual values allowed are "RouteList" (the default value), "MotorIdList" and "All". If a context is
listed that is not allowed via the "MotorDisplaySpecs.AllowedContexts" item, an error message is displayed.
There are two distinct ways of specifying exclusions, and both are optional. The comma-separated list of values
provided with "Exclusions" is probably the easiest to use. However, if the field it applies to is motorid, and multiple
motors are to be excluded, it might conflict with the disallowance of duplicated motor IDs. For that reason, the
"ExclusionsRegex" parameter provides a more powerful pattern-matching capability. You can specify either or both
of these exclusion specifications, but it is not expected to be a useful capability unless you are keeping your AWA
motor lists synchronized with an external system that contains motor entries that should not be included in AWA
routes. If neither of these sub-items is specified in a group, then that field will not cause any motors to be excluded
from the Motor ID or Route tabs' lists, or that in the Route Editor dialog.
There is no facility provided to alter a field's value before appending it to the custom identifier—neither by regular
expression substitution, nor by any other mechanism.
By using the "MotorDisplaySpecs.AllowedContexts=All" item along with the "AppliesTo" sub-item in each grouping,
separate specifications can be created for each context, some for RouteList and some for MotorIdList. This allows
distinct custom motor identifiers to be used in each context. Even though the sub-list of specifications that applies
to any given context may only be a portion of the total list of groupings, the groupings are still listed as a single
contiguous sequence.
Here is an example that displays tree_level_2, tree_level_1, and motorid in the motor lists of the Route
tab and Route Editor dialog, while displaying motorid and tree_level_2 in the Motor ID tab:
MotorDisplaySpecs=4
MotorDisplaySpecs.AllowedContexts=All
MotorDisplaySpec.1.Field=tree_level_2
MotorDisplaySpec.1.BAK.ExclusionsRegex=^(.*\bDefault.*|_TEMPLATE(_BACKUP)?)$
MotorDisplaySpec.1.Format=%s |
MotorDisplaySpec.2.Field=tree_level_1
MotorDisplaySpec.2.Exclusions=_TEMPLATE,_TEMPLATE_BACKUP
MotorDisplaySpec.2.Format=| %s :
MotorDisplaySpec.3.Field=motorid
MotorDisplaySpec.3.Exclusions=_TEMPLATE,_TEMPLATE_BACKUP
MotorDisplaySpec.3.ExclusionsRegex=.*\b[Cc]opy\b.*
MotorDisplaySpec.3.Format=%s
MotorDisplaySpec.3.AppliesTo=All
MotorDisplaySpec.4.Field=tree_level_2
MotorDisplaySpec.4.Exclusions=_TEMPLATE,_TEMPLATE_BACKUP
MotorDisplaySpec.4.Format=: %s
MotorDisplaySpec.4.AppliesTo=MotorIdList
www.megger.com 149