Pre-Process ASN before running rules

Check ASN.1 (container)

Rule Name:

Pre-Process ASN before running rules (container)

Position:

Under: Check ASN.1

Name:

ASN_PreProc

Default:

UN-Checked

Usage:

A container class for rules dealing any pre-processing steps to be performed before other rules are invoked. Typically used to expand macro content.

Note that macro expansion may result in other rules tagging the resulting content as incorrect. When this container class rule is enabled, the global flag preExpandMacros is set to be true for the record. This flag is then used to suppress logic in a few other rules.

This rule holds several other rules beneath it as follows:
[ Click on the arrows below to expand the rule and see its detailed information ]

Show All

Hide All

Expand common macros and correct keyword spelling errors

Rule Name:	Expand common macros and correct keyword spelling errors
Position:	Under: Pre-Process ASN before running rules
Name:	ASN_MacroFull
Default:	UN-Checked
Usage:	Uses the "built-in" table of macro and expands the data type and valid value rule fields when these are seen (surrounded by white space in many cases). This style of macro table, is outdated and the newer, table based, approach is preferred because it can be edited by the end user.

Expand macros using the table of macros found in MEdit_Settings.mdb

Rule Name:

Expand macros using the table of macros found in MEdit_Settings.mdb

Position:

Under: Pre-Process ASN before running rules

Name:

ASN_MacroTable

Default:

UN-Checked

Usage:

Uses the Medit table of macros "Macro_Expand_ASN" and expands the matching string when found in the data type field of the current record. This style of macro table is preferred over the older built-in one because it can be edited by the end user.

Caution should be used when editing this table not to introduce ill-formed ASN, the entries are presumed correct and not checked. Also, consider the order in which the comparisons are made and consider any sub-string problems you may create. In general, check the longest string first.

<-LAST TOP NEXT->