Menus
File Menu
| New | Used to create dynamic, static, PDF or inherited documents, as well as external transaction files. |
| Open | Used to open REQ files as well as transaction XML
files. Note: You can open a single requirements
file within multiple instances of Requirements Editor. When
working with multiple instances, consider the impact of the
possibility of overwriting a transaction file with changes
from another instance. |
| Re-open as Writable | This option is available only when the current file is locked for editing. Selecting this option closes the file and reopens it in a writable (editable) state. |
| Close | Closes the file that currently has focus in the tool. This will close transaction XML or REQ files. |
| Save/Save As/Save All | Used to save changes made to the file that has focus in the tool. Save All saves all files that are open in the application, regardless of their focus status. |
| Properties | Shows the different properties of the document that currently has focus. |
| Recent Files | Allows you to quickly open one of the ten most recently opened files. |
| Exit | Closes the application |
Edit Menu
| Undo/Redo | Undo/Redo the last change that was made. |
| Cut/Copy/Paste | Works like standard Cut/Copy/Paste functionality. You can use these three options on elements in the Outline Editor and Transaction tabs. |
| Delete | Removes the selected element from the file. A message is displayed prompting you to confirm the action. |
| Duplicate | Only usable in the Outline Editor tab. This creates a copy of the currently selected element (or elements). The copy is added to the tab. |
| Select All | Selects all existing elements within the Field Grid, Package Rules or Notes tab. |
| Move Up/Down | Only usable in the Outline Editor tab. This moves the currently selected element (or elements) up or down in the tree structure of elements. |
| Decrease/Increase Indent | Only usable in the Outline Editor tab. This moves the currently selected element (or elements) to a shallower or deeper level in the tree structure of the elements. |
| Find | Normal find functionality. It works in many Requirements
Editor windows/tabs. Attention: When the Find feature is called from the Outline Editor
tab: See also:
|
| Replace | Normal replace functionality. You should avoid using this functionality for the time being. |
| XPath Location | Allows you to provide an XPath in order to display its location inside the REQ. |
View Menu
| Expand/Collapse All | Only usable in the Outline Editor tab. This expands or collapses all tree nodes in the tab. |
| Expand/Collapse All Attributes | Expands or collapses all attribute nodes inside the current document in the Outline Editor. |
| Messages | Displays or brings focus to the Messages window. |
| View Windows Commands | |
| Active Conditions | Toggles the display of the
selected View item within the View pane. Select a menu command to the left to view detailed information for each. |
| Build Errors | |
| Cell Contents | |
| Content Errors | |
| Deprecated Items | |
| Notes | |
| Precedence Status | |
| PTR Editor | |
| Validation Errors | |
| Normal Page Width Page Height Full Page |
Selects how the PDF is sized within the PDF tab. |
| Previous Page Next Page First Page Crtl+Home Last Page Ctrl+End |
Allows you to navigate between pages of a multi-page PDF. |
| Messages Ctrl+M | Displays or brings focus to the Messages window. |
PDF Menu
| Import PDF | Used to import a PDF for use as a document template. |
| Export PDF | Used to export the document as a PDF template. |
| Import Field Grid Rules... | Used to import field grid rule data from a spreadsheet. For more information, refer to Import Field Grid Rules. |
Static Menu
| Import XTemplate | Used to import XTemplates for static documents. |
| Export XTemplate | Used to export XTemplates for static documents. |
| Continuation Page Setup | Used to add continuation pages to static documents. |
| Find Rules for this Public Name | Used to find rules for a given public name. |
| Find Definition for this Public Name | Used to find definitions for a given public name. |
| Find Rules and Definitions for all Public Names | Performs a combination of the two options above. |
| Verify Reused Rules | Verifies any revisions for rules. |
Transaction Menu
| Create Transaction > From Document Rules | You can create a transaction internally or externally. If opting for an external transaction, you create a transaction xml file and then build it within Requirements Editor. The external transaction is not linked to the REQ. Rather it’s treated as another tab for just working on that xml. |
| Create Transaction > From Package Rules | Similar to Create Transaction from Document Rules, but uses Package Rules as a source. |
| Import Transaction | Used to import transaction XML. |
| Export All Transactions | Allows you to export all embedded transactions simultaneously. |
| Save Transaction As | Used to save transactions. It is available by selecting Transactions > Save Transaction As or by right-clicking the transaction tab and selecting Save As. For more details, refer to Saving Transactions |
| Scrub and Save Transaction As | Used to mask data inside a transaction when compared to the original transaction. For more information, refer to Scrub and Save Transactions As. |
| Change Transaction Name | Used to change the name of transactions. |
| Validate Transaction | Used to validate whether the transaction XML is correctly
constructed. During this process, a list of deprecated items is displayed as a list of XPaths. For more information, refer to Validating Transactions. |
| Remove All Transactions | Permanently removes all transactions from the document. |
Test Menu
| Build Document | Runs a syntax check on REQs. Any incorrect structure or PTR will show build errors. For more information, refer to Building a Document. |
| Execute Document | Creates and displays a PDF version of the document, based on the transaction XML you provide. For more information, refer to Executing a Document. |
| Execute Package Rules | Creates and displays a PDF which outlines each package rule and if the document was auto-selected or suggested for each of them. For more information, refer to Executing a Document. |
| DocViewer | Allows you to view and save a requirements file as rendered through the Working with DocViewer engine. |
| Test Document | Allows you to test the current document by select multiple transactions and generating a PDF for each one. For more information, refer to Testing a Document. |
Reports Menu
| Generate Preview | The Generate Preview command allows you to view a requirements files in the format that closely resembles how the eventual published file will appear as a generated PDF and includes a listing of all the data points (DTAs) contained in the file as well as any invalid rules or missing GDD names/Public names. For more information, refer to Previewing a Document. |
| Generate HTML Outline | The HTML Outline command allows you to view an HTML rendered version of the requirements file as it appears in the Outline Editor. For more information, refer to HTML Outline. |
| Export Field Grid | Allows you to export the field grid data as an Excel (.xslx) file. For more information, refer to Export Field Grid. |
| Export XPaths | Creates a text file that includes a list of all XPaths within the current document, including XPaths located in the Package Rules tab. For details, refer to Export XPaths |
| Duplicate PTRs Report | Allows you to view existing duplicates of PTRs in a single spreadsheet. For more information, refer to Duplicate PTRs Report. |
| Find Forms Using this Rule* | Shows documents that use a given rule. This option is available only for static documents. |
|
|
Tools Menu
| Spell Check | Runs the spell check process on the active tab. |
| Options | Displays the Options, providing access to various options to tailor the working environment. |
| Clear Temp Files | Allows you to manually clear outdated local files and
temporary data generated by Requirements Editor. This option is
available from Tools > Options > Environment > General under the General tab. By default, Requirements Editor now automatically purges local files every 30 days to prevent excessive disk usage. You can adjust the purging period or use the Clear Temp Files button to clear data immediately. This feature helps manage storage, especially for users working with many branches or large databases, and is similar to the functionality in the Data Dictionary Viewer tool. |
| Refresh Authoring Files | Whenever you run the Refresh Authoring Files command or change the web service, the style sheets, images, etc. are all pulled into the core folder. This helps to ensure all associated files are available. |
| Refresh Schema Files | Allows you to manually refresh schema files. |
| Freeze Content References | Prevents content references from being updated. |
| Unfreeze Content References | Unlocks all content references and allows them to be updated. |
Window Menu
| Float, Dock, Auto Hide, Hide | Allows you to set how the currently selected document tab is displayed. For more information, refer to Arranging and Docking Windows. |
| Auto Hide All | Causes all View Windows to be collapsed to the bottom of the application. Selecting a hidden tab expands it for viewing and editing purposes until another hidden tab is selected. This can be undone by selecting Window > Reset Window Layout. |
| Close All Documents | Closes all documents currently open in Requirements Editor. |
| Reset Window Layout | Resets all open Authoring Tabs and View Windows to display in the default layout. |
Help Menu
| Online Help | Opens the online help documentation (this document). For more information, refer to Documentation. |
| About Requirements Editor | Displays version information, Expere Engine Version, and installed packages. For more information, refer to Version Information. |