PTR Editor

The PTR Editor window provides an editing view for product technical rules (PTRs) contained within a dynamic or static requirements files. You may edit business logic and technical rules as well as navigate to specific locations in the files where the condition is used. The PTR Editor also presents options to view and edit the output format, GDD name, and Public name along with changing the formatting of the PTR within the Outline Editor and Field Grid.
Note:
  • The PTR Editor must be populated with business logic and PTR to enable editing.
  • If the rule comes from a content reference, then Output Format, GDD Name and Public Name, as well as the PTR and business logic, are read only.
  • The PTR text box contains ten lines of visible text with a scroll bar to view any lines that span beyond ten lines.
  • Copying text from the PTR text box is enabled.
The PTR Editor window is available by:
  • clicking the PTR Editor option in the View > Other Windows menu and also through the standard toolbar in the Other Windows list.
  • pressing Ctrl+Alt+P on your keyboard.
The PTR Editor is available for dynamic and static requirements files and is available from the Outline Editor and Field Grid when a field is selected. This is an example of the PTR Editor when a Condition is active in a dynamic requirements file.

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.
PTR Editor Features
Locations Displays the number of times the condition is used as well as provides a link to each location.
Output Format Used to define how certain entries are presented in the system. For more information, refer to Output Formats. Formats include:
  • Checkbox
  • d mmmm yyyy
  • m/d/yy
  • m/yy
  • mm/dd/yy
  • mm/dd/yyyy
  • mm/yy
  • mmmm d
  • mmmm d, yyyy
  • mmmm, yyyy
  • dd mm yyyy

  • dd/mm/yy

  • dd/mm/yyyy

  • mm dd

  • mm dd, yyyy

  • mm, yyyy

  • d

  • dd

  • dth

  • m

  • mm

  • mmm

  • mmmm

  • yyyy

  • yy

  • hh:mm:ss[24hr]

  • hh:mm A.M./P.M.

  • hh:mm:ss A.M./P.M.

  • $1,234
  • $1,234
  • $1,234.50
  • 0.12
  • .05
  • 01
  • 1234
  • 1,234
  • 1.234.
  • 1,234.56
  • 1,234.567
  • Raw7
  • #th
  • ##th
  • Alpha
  • Alpha Check Amount
  • Alpha Percent
  • 12%
  • 12.%
  • 12.34%
  • 12.345%
  • 12 or 12.34%
  • 12 or 12.345%
  • Raw7%
  • Texas
  • TX
  • String
  • In line
  • Raw
  • RAW IntDisc
GDD Name* The data name used for VMP tech/board and E-Forms content.
Public Name* The name used to define the rule for the BSI tech/board and E-Forms content.
Substitution Name* The data name used when completed with values from the Edit Instance screen.
SuppressUI When Yes is selected, this allows you to suppress warnings that would come from schema validation during the build process.
XPath: Contains an XPath attribute value, used to supply the location to a corresponding SmartDocData element section. Its contents can be text, a data element (DTA), or a combination of the two.
Format Rule Autocorrects the text within the PTR field, including rule completion, case correction, etc. In the following example, the IF statement is not completed. Clicking Format Rule analyzes and completes the rule.

Note: The Format Rule command is automatically run when you change focus from the PTR field to another field via the Tab key or using the mouse.
PTR XPaths Displays a window containing a list of all XPaths in use by the associated PTR.

Note:
  • The total number of XPaths and the rule name are shown in the window titlebar.
  • Displayed XPaths are available to copy to the Clipboard.
  • The window must be closed to continue activities in Requirements Editor.
  • To show only those XPaths for the current scope of the selected rule, select Show only XPaths from the current scope. This feature is not available from the Field Grid nor for static documents.
Font Allows you to change the font used within the PTR Editor fields.
Business Logic A plain English description of the purpose of the data field, or 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. Information entered into Developer Notes is also viewable in the PTR Editor tab of the Outline window.
Current Scope Displays the scope that applies to the selected PTR rule.
Note: If the selected rule is not applicable within the Field Grid, it is indicated here.
Full Scope Displays the combined scope of all rules, except for the current scope.
PTR Displays and allows you to edit the Product Technical Rule for the condition. For more information on using the PTR Editor, see Product Technical Rule (PTR) Reference.
* Displayed only if the Rendition plugin is being utilized

Instances

Selecting an item in the PTR window causes the number of instances that item is found to be displayed:
  • in the DTA.ID:

  • in the location drop down list: