Release Notes

TrackRecord 6.1.0

May 20, 2002

 

 

Obtaining the Latest Release Notes
System Requirements
What's New
Technical Notes
Known Issues
Contacting Compuware Technical Support

 

Obtaining the Latest Release Notes  back to top 

If you accessed this document from the product CD or from the program shortcuts on your desktop, you may not be reading the latest release notes. For the most recent information, go to FrontLine, Compuware's technical support web site. After logging onto FrontLine, select your product from the drop-down list and click Go. On the left side of the page, click the Documentation link. You will find the latest release notes listed with the other product documentation.


System Requirements  back to top

TrackRecord has the following minimum system requirements:

TrackRecord Server

AutoAlert

WebServer

TrackRecord Clients


What's New in Release 6.1.0  back to top

This section describes the new features available in this release.

Improved AutoAlert Functionality
TrackRecord's AutoAlert utility notifies users via email of changes that might be of interest to them. AutoAlert includes the following enhancements:

WebServer File Attachment
WebServer users can now attach files to forms, open attachments, and delete attached files. For example, a WebServer user may want to attach a Microsoft Word document or screenshot to a defect. This feature is available for users with Microsoft Internet Explorer and Microsoft Internet Information Server (IIS) 4.0 or later.

Check Database Scheduling
The Check Database feature (used to check database items, correct errors, and promote database integrity) can now be scheduled to run automatically. This feature requires Microsoft Internet Explorer 4.0 or later.

Enhanced Documentation
TrackRecord's online help and user manuals have been greatly enhanced to include more topics and easier navigation. To access the help files or user guide from the Start menu, select Programs>Compuware>TrackRecord and choose the appropriate file.


Technical Notes  back to top

This section includes technical information that may affect how you use the product.

File Attachments
The TrackRecord limit on file attachment size per item is 12 MB. After attachment, these files are compressed, stored in attach.dat, and can only be viewed through the TrackRecord client or WebServer. Their compressed physical size when stored in the database can be notably smaller than the original file size (similar to .zip compression ratios).

Using the Check Database Feature
Compuware recommends that you run Check Database from the same client machine each time to keep all resulting information in one log file.

Automatic Update of TrackRecord Server Database
When you upgrade TrackRecord 5.0.0 client or server to TrackRecord 6.0.0 or later, TrackRecord automatically updates its database. You will receive a warning message that only an administrator can update the database. Other users cannot connect to the database until the administrator makes the update. Note that TrackRecord 6.1.0 does not update a 6.0.0 database-- they are fully compatible.

Opening Concurrent Databases
If 12 databases are opened concurrently and you attempt to open an additional database, an error will display. To open additional databases, modify the Faircom Server configuration. To do so, perform the following procedure:

  1. Stop the Faircom server.
  2. In Windows Explorer, open the configuration file ctsrvr.cfg in the TrackRecord Server directory. The path is C:\Program Files\Compuware\TrackRecord Server by default.
  3. Modify the FILES configuration parameter to a higher value. Compuware recommends that this value be set to the number of TrackRecord databases residing on the server multiplied by 60 (ex. for 10 databases, 10 x 60 = 600 files).
  4. Save and exit the file.
  5. Restart the Faircom server. For detailed instructions on starting and stopping the Faircom server, consult the TrackRecord and Reconcile Installation Guide.

Duplicate Users in the Database
Multiple instances of users and machine names occur in the Active Users Dialog when there are two or more sessions of TrackRecord open with this user name. This can occur in the following instances:

Note: The total number of users listed as logged into the database does not necessarily reflect the total number of licenses being used.

Adding a List of Available Databases to the WebServer Login Window
You can add a drop-down list of available databases to the WebServer login window. To do so, follow these steps:

  1. On the WebServer machine, open Windows Explorer and navigate to the directory x:\Inetpub\cgi-win, where x is the directory with Windows installed on your computer.
  2. Create a text file entitled TRDatabaseList.txt if one does not already exist.
  3. In the TRDatabaseList.txt file, list the names of the databases available on your server. Enter one database name per line. For example, for databases Sample, Demo, and ProjectX, you would list:

Sample
Demo
ProjectX
  1. Log into the WebServer. In the Database field of the login page, verify that the drop-down list appears containing the databases entered in step 3.

Cautions When Creating Fields
If you are, or will be, using the WebServer, ensure that there are no spaces at the end of a field name when creating and naming a new field. This precaution will prevent errors when opening your web page.

Windows NT Error #2041
If you receive a Windows NT error #2041 message when attempting to start the Faircom server, then follow these steps to correct the issue:

  1. On the machine on which the Faircom is installed, search for and delete all *.fcs files.
  2. Restart the Faircom server. For detailed instructions on starting and stopping the Faircom server, consult the TrackRecord Installation Guide.
  3. If the Faircom server is unable to start successfully, open the configuration file ctsrvr.cfg in the TrackRecord Server directory. The default path is C:\Program Files\Compuware\TrackRecord Server.
  4. Delete any lines beginning with the text DUMP.
  5. Save and exit the ctsrvr.cfg file.

Non-supported Languages
TrackRecord does not support double-byte languages, such as Japanese, Korean, and Chinese or right-to-left languages, such as Hebrew and Arabic.

Resetting the Identifier Value
After you have completed an initial test of the TrackRecord workflow, rules, and functionality, you may wish to reset the item's identifier before using TrackRecord in a production setting. To do so, follow these steps:

  1. From the Administrator menu, choose Edit Types. The Choose a Type dialog box appears.
  2. Select a type and click the Edit button. The Type Editor appears. For instance, select Defect to open the Defect item in the Type Editor.
  3. Right-click on the Identifier field. From the context menu, choose Open Identifier. The Field Properties dialog box appears.
  4. Click the Properties tab.
  5. In the Current Counter Value field, enter a new starting identification number. For example if you wish to set the defect identifier to 000001, enter 0.
  6. Close all dialog boxes.

Notice to Netscape Users
If you run the TrackRecord WebServer on a machine running Windows 2000 Professional and attempt to run a web client on the same machine and using the Netscape 4.7x browser, the client will experience performance problems.

Notice to Microsoft Internet Information Server 3.0 Users
Please be advised that TrackRecord no longer includes support for Microsoft Internet Information Server (IIS) 3.0. TrackRecord will, however, continue to support IIS 4.0 or later with ASP. If you have questions or concerns, please contact your Compuware sales representative.

Notice to Novell Users for TrackRecord
Please be advised that TrackRecord no longer includes support for Novell Netware client software. If you have questions or concerns, please contact your Compuware sales representative.

Notice to Netscape Enterprise Server Users
Please be advised that TrackRecord includes support for Netscape Enterprise Server version 4.1 only.

Notice to Windows 95 Users
Because Microsoft Corporation will discontinue support for Windows 95 at the end of year 2001, QACenter Release 4.6 is the final release that will support Windows 95. Although QACenter products may continue to function in a Windows 95 environment, please be advised that our products will not be tested or developed specifically for that platform. Furthermore, Windows 95 users may not be able to receive patches for fixes or new technologies. Compuware is providing this advanced notice so that you will have adequate time to prepare and plan within your organization. If you have questions or concerns, please contact your Compuware sales representative.

Notice to PVCS Users
Please be advised that TrackRecord includes support for PVCS Version Manager 6.5 or later only.

Notice to Novell Users for CSLM Server
QACenter Release 4.6 is the last release that will support Compuware’s Client/Server License Manager (CSLM) server on Novell network servers.

Compuware plans to implement CSLM release 3.2, which uses Globetrotter Software’s FLEXlm 7.0. Globetrotter has announced that FLEXlm 7.0.9 is the last release that will support Novell. With future releases of Compuware products and CSLM, customers who are running the License Manager server on Novell will need to migrate it to one of the supported platforms: Windows 2000, Windows NT, and UNIX versions for Sun Solaris, SunOS, HP-UX, AIX, VMS (new in CSLM 3.2) and LINUX.

Compuware recognizes that Compuware testing tools are an integral component of our customers’ product-release cycle. This pre-notification is intended to assist you in planning the implementation of new releases in your organization. If you have questions or concerns, please contact your Compuware sales representative.

Migrating the License Manager Server from a Novell Server
When implementing CSLM releases beyond 3.2, customers who now use Novell networks to support the License Manager server must move it to a supported Windows or UNIX platform. If you choose to move to a Windows platform, Compuware recommends that the server machine be a Windows NT or 2000 Server, not a workstation. TCP/IP must be enabled on the Windows NT or 2000 Server. If moving to a UNIX platform, refer to your product’s installation guide or the CSLM License Installation Guide to determine the supported UNIX platforms.

Note: Existing license certificates that reside on a Novell License Manager server cannot be used on a Windows or UNIX server. Because the server identification (either NIC or serial number) is part of the key encryption, you must obtain new licenses before activating Compuware products on the Windows or UNIX server. To obtain your new license, e-mail Compuware License Management. You can also contact your sales representative.

After obtaining a new license, install the License Manager on your new server. After installing the License Manager, use the License Administration Utility (LAU) to configure the client machines to access the new license server. Refer to your product’s installation guide or the CSLM License Installation Guide for instructions on installing the License Manager and configuring client machines. On the client machines, you must remove the current settings for FLEXLM_COMM_TRANSPORT and LM_LICENSE_FILE. Then, use the License Administration Utility (LAU) to set the new license location.

If you have questions or concerns about your license, please contact Compuware’s Technical Support at 800.538.7822 in the USA and Canada, and 248.865.5444 in other locations, or via Compuware’s FrontLine support web site at FrontLine.

Upgrading From TrackRecord 5.x to 6.x
Since the release of TrackRecord 5.x, the directory structure has changed and databases are now installed in a different default location. As a result, after you upgrade to TrackRecord 6.x, you must copy your TrackRecord 5.x database folder to the new 6.x database folder.

The following table lists the default location for TrackRecord 5.x and 6.x databases:

VersionSuiteDefault Installation Directory
TrackRecord 5.xQACenterx:\Program Files\Compuware\TrackRecord\Server\Databases
TrackRecord 5.xDevCenterx:\Program Files\Numega\DevCenter\Server\Databases
TrackRecord 6.xQACenter and DevPartner Enterprise Editionx:\Program Files\Compuware\TrackRecord Server\Databases

Moving or Renaming the "Databases" and "Backups" Folders
Compuware recommends that you do not move or rename TrackRecord's Databases or Backups folders. Doing so will cause a loss in TrackRecord functionality. However, you can safely move and rename the subfolders.


Known Issues  back to top

This section describes known issues related to the current release of TrackRecord.

Uninstalling Previous Versions of TrackRecord
If you are running a previous version of TrackRecord, Compuware strongly recommends that you uninstall the previous version and reboot your PC before proceeding with the installation of TrackRecord 6.1.0.

WebServer Calendar Button
The calendar button works with Microsoft Internet Explorer only.

Error When Printing Multiple Help Topics
When printing multiple topics from the help files, a script error displays. This is a bug in the Microsoft HTML Help viewer.

AutoAlert Installation Issue
Performance problems have been encountered when the WebServer, AutoAlert, and TrackRecord server are running on the same dual CPU system. To avoid these issues, Compuware recommends either installing all components on a single CPU system, or installing AutoAlert on a separate machine.

Team Member Association
TR_User is a special tag that identifies the type a user is associated with. In the default schema, this type is "Team Member". Do not create any types that inherit from the type with the TR_User tag associated with it. Doing so could cause problems with TrackRecord users and result in the loss of administrative privileges to the database.

Deleting Fields
When you delete multiple fields, it is best to note the order that the fields were deleted. If you recreate the fields, you must do so in the reverse order that they were deleted. Then, perform a database rebuild and a Check Database to ensure data integrity.

Deleting Hidden Fields
Before deleting fields; ensure that the field is not hidden.

Sharing Mail Queries
Mail queries can be shared with other users and used as a normal query, but AutoAlert will send email notification only to the owner of the query. For example, if an owner of a query selects the Email me option, AutoAlert will send email notification only to the owner. Queries created by the Admin user are the exception. The Admin options are as follows:

OptionsBehavior
Email me option checked, query is Not SharedAutoAlert will send notification to the Admin only
Email me option checked, query is Shared to All (Recommended)AutoAlert will send notification to every user
Email me option selected, query is Shared to one or more groupsAutoAlert will send notification to every user (regardless of group) and operates the same as Shared to all.

Creating New Types
When creating a new assignment type, ensure that you select the type and click New. Do not double-click the assignment type to open the dialog box. Doing so will create empty items and can result in loss of data integrity.

Cut/Copy/Paste Actions
The cut, copy, and paste buttons and actions from the Edit menu in the TrackRecord Windows client are currently unusable. Instead, use the Ctrl+X, Ctrl+C, and Ctrl+V shortcut keystrokes.

Shutting Down AutoAlert Prior to Backup
Prior to performing a database backup, you must manually shut down AutoAlert and then restart it once the backup is complete. Contrary to what is documented in the AutoAlert online help's topic "Enabling Temporary Shutdown", it is not possible to enable a temporary shut down of AutoAlert.

Attaching a File in the WebServer
When attaching a file in the WebServer, select the attachment before clicking the WebServer's Open link. Failure to do so will result in an error message.

Importing Duplicate Items
When importing duplicate items into the database, ensure that the Discard Duplicates option is not selected. Otherwise, the existing item in the database will also be deleted.

Queries With a Multiple Item List Box
A query will not produce expected results if more than one item is in a multiple item list box. To return the defects that contain <value> in the multiple item list box <xyz>, set up the query: "<xyz> is not equal to none" OR "<xyz> is equal to <value>".

Creating Queries From an Outline Report
If you intend to duplicate a query, create it from the Query Editor rather than from an Outline Report.

Stack Bar Graphs
The stack bar graph only displays results from the first page of an Outline Report. To display your Outline Report in a graph, select bar or pie graphs instead.

WebServer Licensing Issue
If an evaluation license is installed on the server and users attempt to access the WebServer, an error message such as maximum number of users reached will be displayed followed by a cgi/itemview.dll error message. In order for the WebServer to work properly, a temporary or permanent license is required.

Outline Report Parent Headers
In the WebServer, clicking three times consecutively on an Outline Report's parent header may cause the request sent to the server to hang. To avoid this situation, click the browser's Back button, or any TrackRecord menu item between clicks.

Adding Child Types to Team Members
Avoid creating child types of the Team Member type as it may disable your Admin account. Instead, constrain fields in your form. If you notice that your default Admin account has become disabled from the User Administration view, do not log out of the Admin account. Contact Technical Support as soon as possible. Creating a backup administrator login is advisable in any circumstance.

Search Parameters
The search string is limited to 33 characters. If it is not possible to modify the search string to fit these parameters, create a query to search for the string.

Search Error
In the Search drop-down, an error will occur if you click on Task and then Feature.

TrackRecord and Reconcile Synchronization
Synchronizing between Reconcile and TrackRecord may become slow when done with large numbers of requirements . To improve synchronization speed, open the Requirement type in the TrackRecord Type Editor, rename the Project field, and remove the associated field tags. Then, open each existing requirement item in TrackRecord and manually clear the Project field (set the value to <none>). For more information or assistance, please contact technical support.

WebServer Installed on a Different Drive Than Windows
If the WebServer is installed on a different drive than Windows, an error may occur or the browser may hang, specifically during an attempt to attach a file. You can avoid this issue by creating a temporary directory on the drive where Windows resides. To do so, perform the following procedure:

  1. On the WebServer machine, create the "C:\Inetpub\wwwroot\TrackRecord\Temp" directory.
  2. Set full access permissions for the directory to Everyone.
  3. Stop and restart the World Wide Web Publishing Service.
  4. Reboot if prompted.

Check Box Items in the WebServer
The check box field does not appear in the WebServer Outline Report.

Duplicate AutoAlert Messages
If duplicate AutoAlert messages are repeatedly sent to the same user, delete the status file and restart the AutoAlert service. To do so, perform the following steps:

  1. Stop the AutoAlert server. For detailed instructions on starting and stopping the AutoAlert server, consult the TrackRecord User’s Guide
  2. .
  3. On the machine on which AutoAlert is installed, locate the status file, TR_<server>_<database>_StatusFile.dat. Where <server> is the server name that contains the database and <database> is the name of the database.
  4. Delete the status file.
  5. Restart the AutoAlert server.
For more information or assistance, please contact technical support.

Associating a Release With a VCS Label
If you receive a Can’t find project in source control error while attempting to associate a release with a VCS label, the release type may not know which TrackRecord project, and consequently VCS project, to associate the label with. To associate a VCS project with a release, you must add a field to the Release type and then associate a VCS label. To do so, follow these steps:

  1. From the Administrator menu, choose Edit Types. You must be logged in as a user with administrative rights.
  2. Select the Release type and click the Edit button. The Type Editor appears.
  3. From the Insert Field menu, choose Single Line Text.
  4. Move and click your mouse at the bottom of the release type. The Field Properties dialog box appears.
  5. On the General tab, enter a name for the field.
  6. Click the Properties tab.
  7. Select VCS project/dir.
  8. Click OK. The new field will appear in the Type Editor.
  9. Follow the procedure in the TrackRecord User’s Guide for associating a release with a VCS label.
Note: You must associate the new field with the same VCS project that the parent TrackRecord project is associated with.


Contacting Compuware Technical Support  back to top

Compuware Technical Support can assist you with all your technical problems, from installation to troubleshooting.

Before Contacting Technical Support
Prior to contacting technical support, gather the following information:

Telephone
USA and Canada: 800.538.7822
Other locations: 248.865.5444

FrontLine Support Web Site
Refer to Compuware's Frontline support web site for fast access to critical information about your product. You can read and print documentation, download product fixes, review frequently asked questions, or directly e-mail Compuware with questions or comments. The first time you access FrontLine, you are required to register and obtain a password.

Compuware Corporate Web Site
Refer to Compuware's corporate web site at http://www.compuware.com for information about Compuware technical support policies and problem resolution process.

Mail
Compuware Corporation
31440 Northwestern Highway
Farmington Hills, MI 48334-2564

 

End of TrackRecord Release Notes
(C) 2002 Compuware Corporation. All rights reserved. Unpublished rights reserved under the Copyright Laws of the United States.