Field Grid

The Field Grid tab allows you to scroll through all data points (DTAs) and identify any invalid rules or missing GDD names/Public names. This is helpful after the PTRs are complete to be able to quickly scroll through all of the PTRs and identify possible validation issues. Potentially invalid rules are highlighted in yellow, but note that some rules that will not validate in the field grid are actually valid rules. The Outline Editor tab is much more accurate for validating PTRs.

Note: When you import Field Grid rules from a spreadsheet using the Import Field Grid Rules... menu option, Requirements Editor matches partial field names that include underscores, numbers, or hashes. When a match is found, Requirements Editor updates the Business Logic, PTR, Is Fillable Field, and Output Format columns in the Field Grid tab. If you import rules and do not see expected updates, refresh the Field Grid view or reopen the REQ file to verify changes.

The following features appear in the Field Grid:

Type	Allows you to filter the Field Grid by rule type (DTA, COND, ITR). Example: Entering "ITR" in the Rule Type field and selecting Apply filters the Field Grid so that only rule names containing "ITR" appear. Selecting Clear resets the field grid so that all entries appear.
Name	Allows you to filter the Field Grid by rule name, either through text or numerals. Example: Entering "46" in the PTR field and selecting Apply filters the Field Grid so that rules containing the numerical value "46" within the PTR appear. Note that multiple entries may appear if "46" is present in the rule name. Selecting Clear resets the field grid so that all entries appear.
PTR	Allows you to filter the Field Grid by a text string within the PTR column. Example: Entering "Ethnicity" in the PTR field and selecting Find filters the Field Grid so that rules containing the string "Ethnicity" within the PTR are displayed. Selecting Clear resets the field grid so that all entries appear.
Rule Name	A unique ID for each data field entered.
Business Logic	A plain English description of the purpose of the data field, or rule. This is not used for EPM content.
Product Technical Rule (PTR)	The PTR represents the processing instructions, or code, that defines the behavior of the rule. This is not used for EPM content.
Developer Notes	Allows you to add internal notes to a PTR. This information is not customer facing and is stripped out when building the document. Special characters ( <, >, &, ', ") and line returns are honored.
Suppress Warnings	When the checkbox is selected, this will allow you to suppress warnings that would come from schema validation during the build process.

If a property is editable, clicking in the desired cell will allow you to edit the content.

Note: When editing a PTR, an alert appears if you enter a value that already exists in the document rules. The alert is simply for notification of a duplicate and the duplicate value is saved regardless.

The Overflow column is available in the Field Grid for Embedded PDF documents. This column allows users to view and export overflow settings for each field, making it easier to validate and document Overflow behaviors across multiple forms. When exporting the Field Grid, the Overflow column is included in the output, saving time and reducing manual effort for reviewing overflow data.