Archived: Requirements Gateway 2012 Known Issues

Overview

This document has been archived and is no longer updated by National Instruments.

This document contains the Requirements Gateway 2012 known issues
that were discovered before and since the release of
Requirements Gateway 2012. Not every issue known to NI will appear on this
list; it is intended to only show the severe and more common issues
that can be encountered.

Each Issue appears as a row in the table and
includes these fields:

Issue ID - the number at the top of each of the cells in
the first column. When you report an issue to NI, you may be given this
ID, you can also find IDs posted by NI on the discussion forums or in
Knowledge Base articles.

Legacy ID (optional) - If an issue has a legacy ID from NI's legacy/deprecated bug reporting database, you will see it appear on a separate line directly below the Issue ID in the table, or to the right of the Issue ID in the table of contents (separated by a space).

Issue Title: in italics - it describes the issue in one
sentence or less

Problem Description - a few sentences which describe the
problem in further detail. The brief description given does not
necessarily describe the problem in full detail, and it is expected
that you might want more information on an issue. If you would like
more information on an issue feel free to contact NI (contact
information below) and reference the ID number given in the document.

Workaround - possible ways to work around the problem. The
workarounds that appear in the document are not always tested by NI and
are not guaranteed to resolve the issue. If a workaround refers you to
the NI KnowledgeBase, please visit www.ni.com/kb/ and enter that KB
number in the search field to locate the specific document.

Reported Version - the earliest version of TestStand ATML Toolkit the
issue was reported in. If you discover the issue appears in an earlier
version of TestStand ATML Toolkit than is reported in this field, you can report that to NI (contact information below) to have the field updated.

Resolved Version - version the issue was resolved or was no
longer applicable. If an issue has not been resolved "N/A" will be
reported.

Date Added - the date the issue was added to the document
(not necessarily the reported date)

Table of Contents

Document Organization:

The Known Issues Document is divided into two separate tables appearing in two separate Developer Zone documents. The following document displays the issues by issue category.

Known Issues by Date
For those who wish to locate the newly reported issues, we have also published another version of the known issues table sorted only by date the issue was added to the document.

Contacting NI

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. 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. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.

The Application stay on top option applies only to the main window
If you enable the Application stay on top option on the General tab of the Options pane of the Configuration dialog box, the main window always remains in front of other application windows, such as the Configuration dialog box. This can cause other application windows to appear hidden if the main window completely obscures them.

Expressions pane does not support multi-line strings
When you use the Expressions pane of the Configuration dialog box to test regular expressions, neither the Expressions pane nor the tooltip display results with multiple lines.

Project passwords are limited to eight characters
You can specify a project password that exceeds eight characters, but Requirements Gateway uses only the first eight characters as the stored password.

Multi-byte characters in a requirement element name you create on the Types pane might break the hierarchy of requirements
When you edit the definition of a requirement element on the Types pane of the Configuration dialog box and you use multi-byte characters, such as Chinese, any child requirements definitions move to the top level of the requirement hierarchy after you save the type and and edit it again.

Selecting a MATRIXx catalog does not cause MatrixX to become the active application if the catalog is already loaded
When you navigate from Requirements Gateway to MATRIXx and the selected MATRIXx catalog is already loaded, MATRIXx does not become the active application. If a dialog box launches when you attempt to navigate, Requirements Gateway appears to hang because the dialog box might appear below the Requirements Gateway window.

A Link element in a Critical Failure Stack section of a TestStand XML Reports document can navigate to the incorrect step result
When you navigate from a Link element in a Critical Failure Stack section of a TestStand XML Reports document that contains more than one UUT report, Requirements Gateway might navigate to a step result in a different report. This occurs because the result ID that Requirements Gateway uses is not unique between different reports.

Requirements Gateway crashes when you generate a report that contains a Generation structure with a name that matches the name of the report
If a custom report contains a Generation structure with a name that matches the name of the report, Requirements Gateway crashes when you attempt to generate the report.

An overwrite occurs when snapshots have identical timestamps
If you create a snapshot with the same timestamp as an existing snapshot, the new snapshot replaces the existing snapshot. Because the timestamp resolution is one minute, this can occur with snapshots taken within the same minute.

Workaround: Before taking a snapshot, ensure that the latest existing snapshot timestamp does not match the current time.

Requirements Gateway might crash on exit after exporting documents to IBM Rational RequisitePro
When you attempt to export a document to IBM Rational RequisitePro and the document contains an attribute with a name that matches any multi-selection attributes that RequisitePro predefines, Requirements Gateway returns an error that indicates that the property must be set from the ListItemValue object text. If you exit Requirements Gateway after this operation, Requirements Gateway crashes on exit.

The Large Code type does not recognize new files automatically in some cases
If you use the Large Code type to analyze a directory on a disk that is formatted using the 32-bit file allocation table (FAT32) method the Large Code type does not recognize when new files are added to the target directory, requiring you to reanalyze the document manually. This behavior occurs because the directory date does not change on FAT32 formatted disks when new files are added, and the type uses this information to determine when reanalysis is required.

The Microsoft Word types do not support images with JPEG format
If you specify a document of the Word type and the Word project document source file contains JPEG images, Requirements Gateway does not recognize the images and does not display the image previews in the main window.

RequisitePro can return an error on exit when launched from Requirements Gateway
If you launch IBM Rational RequisitePro from Requirements Gateway by double-clicking a folder under a RequisitePro document in the main window, RequisitePro returns an error on exit that indicates that the selectExplorerKey collection is empty.

Requirements Gateway can navigate to incorrect text when browsing to an element
When you browse to an element in a Microsoft Word document and the Word document contains text for a requirement or section element that appears more than once, Requirements Gateway navigates to the first instance of the text, even if the next instance of the text represents the actual requirement or section.