Each Issue appears as a row in the table and includes these fields:
Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us.
The following items are Bug Fixes in NI Requirements Gateway 2014.
| ID | Legacy ID | Fixed Issue | Issue Details |
|---|---|---|---|
| 49111 | 3XM8N4G0 | Requirements Gateway cannot analyze a Telelogic DOORS module if the module name ends with a space character. | Requirements Gateway cannot analyze a Telelogic DOORS module if the module name ends with a space character. |
| 160549 |
| Requirements Gateway does not correctly analyze folders in a LabVIEW project library | If a LabVIEW project library (.lvlib) file contains virtual folders, Requirements Gateway displays the Invalid section level rule violation when you analyze the project. |
| 173426 |
| Requirements Gateway does not prompt you reanalyze a project after you modify a VI in a LabVIEW project | If you configure a Requirements Gateway project document to analyze a LabVIEW project, Requirements Gateway does not prompt you to reanalyze the Requirements Gateway project if you modify a VI in the LabVIEW project. |
| 173467 |
| You cannot navigate directly to a LabVIEW control or global variable from Requirements Gateway | When you navigate to an element within a LabVIEW global variable or control (.ctl) file, LabVIEW launches but does not open the file. |
| 228855 |
| Browsing for Telelogic DOORS modules can fail when you are using Requirements Gateway in Evaluation Mode | Browsing for Telelogic DOORS modules can cause licensing errors when you are using Requirements Gateway in Evaluation Mode. |
| 279354 |
| Saving a project to the desktop with Windows 7 (64-bit) disables the Add a document button | If you save a Requirements Gateway project to the desktop on Windows 7 (64-bit), the Add a document button is disabled on the Project pane of the Configuration dialog box. |
| 292000 |
| Requirements Gateway incorrectly evaluates VIs with the same name saved in different project libraries | If a LabVIEW project contains multiple project libraries and two or more of the libraries contain a VI of the same name, Requirements Gateway does not recognize that the VIs are in different application instances and displays the VIs in red in the main window. |
| 297791 |
| Clicking empty space on the Attributes tab of the Types pane can cause Requirements Gateway to crash | If you left- or right-click the empty space in the Available values control on the Attributes tab of the Types pane of the Configuration dialog box, Requirements Gateway crashes under the following conditions: <ul><li>The Attribute tab lists some attribute values in the Available values control</li><li>You do not select any value before you click the white space</li></ul> |
| 302064 |
| Front panel and block diagram images do not display for a LabVIEW document when you enable the Intermediate File option | When you select the With Images variable and you enable the option in the Intermediate File column on the Details tab of the Project pane of the Configuration dialog box for a document of the LabVIEW type, Requirements Gateway does not display front panel and block diagram images. |
| 305809 |
| Requirements Gateway does not correctly convert multibyte characters in LabVIEW components for an intermediate file | Requirements Gateway does not correctly convert multibyte characters in LabVIEW components for an intermediate file. The LabVIEW conversion tool does not insert the proper XML tag to enable multibyte support. |
| 308873 |
| Requirements Gateway does not to launch if the PATH environment variable contains more than 2048 characters | Requirements Gateway does not to launch if the PATH environment variable contains more than 2048 characters. This issue can occur each time you try to launch Requirements Gateway until you modify the PATH variable to contain fewer than 2048 characters. After the first time you launch Requirements Gateway successfully, the issue does not re-occur, even if you later modify the PATH variable to again contain more than 2048 characters. |
| 327378 |
| Using the clipboard to copy a requirement element to a new type definition might cause Requirements Gateway to crash | If you use the Types pane context menu to copy a requirement element from a type and paste it into a new type, Requirements Gateway might crash and display the Internal error 10713 error. |
| 335816 |
| An error can occur when you export multiple TestStand sequence files to Telelogic DOORS | When you use a single Requirements Gateway project document to define multiple TestStand sequence files and you export the document to Telelogic DOORS, you might receive the Can't find object with parent "MainSequence" error. |