Release Notes

TrackRecord 06.02.00

February 23, 2004

 

System Requirements
What's New
Technical Notes
Known Issues
Contacting Compuware Technical Support

System Requirements  back to top

This section describes the minimum requirements for running the TrackRecord Windows Client.

Client Requirements

Note to Microsoft NT 4.0 users: TrackRecord 6.2.0 provides tolerance support only for this platform. Tolerance support is limited to providing existing fixes and workarounds for TrackRecord users on this environment. No new fixes or development will be done against this platform, and TrackRecord 6.2.0 will be the last release of TrackRecord to support this operating system. This applies to all components of TrackRecord that may be executed on NT 4.0 platform.

Web Browser Requirements

The following system requirements are necessary for users to access the WebServer through a browser from their client machine:

Note to Microsoft Internet Explorer 5.5 users: TrackRecord 6.2.0 provides tolerance support only for this browser version. Tolerance support is limited to providing existing fixes and workarounds for TrackRecord users on this environment. No new fixes or development will be done against this platform, and TrackRecord 6.2.0 will be the last release of TrackRecord to support this browser version.

Note to Netscape users: TrackRecord 6.2.0 provides only tolerance support for the Netscape 4.7x browser. Tolerance support is limited to providing existing fixes and workarounds for TrackRecord users on this environment. No new fixes or development will be done against this platform, and TrackRecord 6.2.0 will be the last release of TrackRecord to support this browser platform.

Optional Components

The following sections detail the minimum system requirements necessary for installing each optional TrackRecord component.

Database Server (FairCom) Requirements

All the client requirements listed previously, as well as the following minimum system requirements, are necessary to install a server that will house the database. This component can be installed on a central server on your network. A minimum of one server must be installed on a network for database access.

AutoAlert Requirements

All the client requirements listed previously, as well as the following minimum system requirements, are necessary for installing TrackRecord’s email notification service:

Note: Microsoft Outlook is recommended on the Server where AutoAlert is installed to facilitate configuration and testing of the mail profile.

WebServer Requirements

All the client requirements listed previously, as well as the following minimum system requirements, are necessary for the machine upon which the WebServer component is installed:

Note to Microsoft IIS 4.0 users: TrackRecord 6.2.0 provides tolerance support only for this platform. Tolerance support is limited to providing existing fixes and workarounds for TrackRecord users on this environment. TrackRecord 6.2.0 will be the last release of TrackRecord to provide any support for IIS 4.0.

What's New  back to top

This section describes the new features available in this release.

Release 06.02.00

Improved WebServer Usability and Performance

TrackRecord's WebServer Usability and Performance have been significantly improved. The response time for WebServer is quicker, and the improved interface makes it easier to navigate. The process for adding new defects and modifying existing defects has been streamlined for ease of use. 

Redesigned Search Capabilities

Find database information quickly with TrackRecord's redesigned Windows Client and WebServer search capabilities. For example, you can search for all defect items that contain a specific name in any field. 

Enhanced Shipped Defaults

TrackRecord's default and sample workflow and database, types, and templates are now documented in the Getting Started chapter of the User's Guide. 

Technical Notes  back to top

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

Updating TrackRecord 6.1.1 Databases with the New DevPartner Product Names.

TrackRecord 6.2 includes a utility for updating 6.1.1 databases with the new DevPartner Studio product names. Documentation for using the database conversion utility is located in the Program Files\TrackRecord directory, in the file named releasenotes-cvt.html.

Upgrading From Previous TrackRecord Releases

The TrackRecord directory structure has changed and databases are now installed in a different default location. As a result, after you upgrade to TrackRecord 06.02.00, you must copy the subfolders of your TrackRecord database folder to the new database folder. The following table lists the default location for TrackRecord 5.x and 6.x databases:

Version Suite Default Installation Directory
TrackRecord 5.x QACenter x:\Program Files\Compuware\TrackRecord\Server\Databases
TrackRecord 5.x DevCenter x:\Program Files\Numega\DevCenter\Server\Databases
TrackRecord 06.00.00 and 06.01.00 QACenter and DevPartner Enterprise Edition x:\Program Files\Compuware\TrackRecord Server\Databases
TrackRecord 06.01.01 and 06.02.00 QACenter and DevPartner Enterprise Edition x:\Program Files\Compuware\TrackRecord\Databases

Running TrackRecord WebServer on Windows Server 2003

Before running TrackRecord WebServer on Windows Server 2003, perform one of the following procedures to configure your server. If you do not, you will receive a "file not found" error when trying to access the WebServer home page.

Configure the server to allow ISAPI extensions:

  1. On the server where the TrackRecord WebServer is installed, click the Start button and then choose Control Panel>Administrative Tools>IIS Manager.
  2. In the IIS Manager tree, right-click on the Websites folder and choose Properties from the popup menu.
  3. On the Properties dialog box, click the Service tab.
  4. Select the option Run WWW service in IIS 5.0 isolation mode.
  5. Click OK.
  6. In the IIS Manager tree, click the Web Service Extensions folder.
  7. In the right pane, right-click on the All Unknown ISAPI Extensions entry.
  8. On the popup menu that opens, choose Allow.
  9. On the IIS Manager message that opens, click Yes.

Create a new application pool

  1. On the server where the TrackRecord WebServer is installed, click the Start button and then choose Control Panel>Administrative Tools>IIS Manager.
  2. In the IIS Manager tree, right-click on the Application Pools folder. From the popup menu that opens, choose New>Application Pool. The Add New Application Pool dialog box opens.
  3. In the Application pool ID field, type a name for the new application pool. For example, cgi-win.
  4. Select the option Use default settings for new application pool and click OK.
  5. In the IIS Manager tree, right-click on the icon for the application pool you just created and choose Properties from the popup menu.
  6. Click the Identity tab.
  7. In the Predefined field, choose Local System and click OK.
  8. Click Yes on the IIS Manager message that opens.
  9. In the IIS Manager tree, click the Web Sites folder. Under the Default Web Site icon, right-click on cgi-win and choose Properties from the popup menu.
  10. In the Application pool field, choose the application pool you created previously.
  11. Click OK.
  12. In the IIS Manager tree, click the Web Service Extensions folder.
  13. In the right pane, right-click on the All Unknown ISAPI Extensions entry.
  14. On the popup menu that opens, choose Allow.
  15. On the IIS Manager message that opens, click Yes.

Other Notes

Import Effects On Workflow

Importing causes the workflow to lose some of its status/action relationships. After these relationships are recreated, the workflow operates normally.

Receiving an “Active Users” Message When Editing Workflow or Edit Types

When you log on to TrackRecord Client as an administrator and begin to edit the Workflow or Edit Types, a message may appear informing you that active users are logged on.

The message box also appears when multiple Admin users are logged on at the same time. Making changes to the Workflow or Edit Types in this situation may cause the database to react adversely.

Starting the Workflow Editor from the client causes a second login to the TrackRecord database. This occurs because the Workflow Editor is a standalone executable. The application cannot detect that it is the same user logging on again.

The Continue button will appear only if multiple logins of the Admin user occur, and no additional users are logged on. Click Continue to edit the Workflow or Edit Types. Click Send Message to send a brief message to all the users logged on to the database. Click Cancel to exit without loading the editor. Click Force Users Off to force all users off the database.

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.

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 05.00.00 client or server to TrackRecord 06.00.00 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 06.02.00 does not update a 06.00.00 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 directory. The path is C:\Program Files\Compuware\TrackRecord 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 Installation Guide.

Cautions When Creating Fields

The maximum length of a field name is 31 characters.

If you are 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.

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.

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.

Using AutoAlert with MAPI

After the AutoAlert software is installed, you must create a mailbox and mail profile for AutoAlert’s use. You can do so using your preferred information service, such as the Microsoft Exchange Server. To do so, follow these steps:

  1. Create a mailbox for AutoAlert’s use. Consult your mail service’s documentation for instructions on creating mailboxes.
  2. Create a profile named AutoAlert that has access to the mailbox.
  3. Since access to the mailbox is through a service, the service must run as a user that can access the mailbox.

Creating New Users When Using AutoAlert

When creating a new user, any queries marked for electronic notification that apply to the new user will return all results during the next AutoAlert poll. This may result in a large volume of AutoAlert emails being sent to the new user during the first AutoAlert poll.

Troubleshooting WebServer Login Failure

If a WebServer login fails, you will not receive an error message from within DCOMCNFG. Instead, when an attempt is made to login to a database through the WebServer, you will receive an automation error indicating that the configured identity is not correct. This is due to a DCOMCNFG login failure. To remedy this situation, ensure that the log in information is correct and ask a network administrator to grant the NT account "log on as a service" privileges.

Administrative Changes While Running the WebServer

When making changes to the type structure, templates, user and group administration, rules, etc., these changes will not be reflected to the WebServer component if there are active Web session processes running. To ensure that your updates are immediately reflected in the WebServer, follow these steps:

  1. On the WebServer machine, open the Task Manager.
  2. Click the Processes tab.
  3. Select TRWebSessionHost and click the End Process button. Repeat this step for all instances of TRWebSessionHost.
  4. Select TRWebDBHost and click the End Process button.
  5. Exit the Task Manager.
  6. Log on to the WebServer.

Disabling the FairCom Service

To ensure that the FairCom remains stopped, disable the FairCom service as described in the Installation Guide.

Known Issues  back to top

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

Installation

Uninstalling Previous Versions of TrackRecord

If TrackRecord version 06.01.01 or earlier is installed on your computer, or if you have a Beta version installed, Compuware strongly recommends that you uninstall the previous version. If prompted, reboot your PC before proceeding with the installation of TrackRecord.

WebServer

Windows Client and WebServer Installed on the Same Machine

If the TrackRecord Windows client is installed on the same machine as the WebServer and a Web session consumes a license prior to the Windows Client, the Windows Client will not start. This happens because as Web clients log into the WebServer, license calls are made from the WebServer machine to the License server. To remedy this situation, follow these steps:

  1. Ensure that all users are logged off of the WebServer.
  2. From the WebServer machine, open the Task Manager.
  3. Click the Processes tab.
  4. Select Nmdbinfo.exe and click the End Process button.

Note: If you receive an access denied error, try again in 40 minutes. If this is too long to wait or you still receive an access denied error, reboot your machine.

WebServer and TrackRecord Client on the Same Machine with a Trial License

If you have a trial license and install TrackRecord and the TrackRecord WebServer on the same workstation, you must start TrackRecord before starting the WebServer or your system may hang. If this happens, reboot. Then, start TrackRecord before starting the WebServer.

Viewing a File Attachment in the WebServer

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

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. This can be configured with the License Administration Utility.

Check Box Items in the WebServer

The check box field is read-only in a WebServer Outline Report.

Printing Outline Reports

When printing an Outline Report in the WebServer, click in the frame containing the data that you wish to print before clicking the Print icon.

Modifying or Renaming the Attachments Field

Compuware recommends that you do not rename or modify an Attachments field or its underlying type. Doing so will result in an error when attempting to attach a file in the WebServer.

Sorting Columns in an Outline Report

In the WebServer, Outline Report columns are read-only and can only be sorted in the TrackRecord Windows Client. To change the way your Outline Report columns are sorted, follow these steps:

  1. Close any open WebServer sessions.
  2. If you have not already done so, open the TrackRecord Window’s Client.
  3. Open the Outline Report that you wish to configure.
  4. Select a parent header.
  5. From TrackRecord’s View menu, choose Sort>column name. Repeat this step for each column you wish to sort.
  6. Repeat steps 3-5 for each parent header.
  7. After you have completed your changes, save the Outline Report.
  8. Log in to the WebServer and open the modified Outline Report.

Administrative

Using a Batch File to Run Check Database

An Administrator user running a check database cannot have a home page set in their browser if they are using a batch file to run check database. The home page will cause a dialog to appear at the end of the check. This will cause the batch file to hang.

Hiding the Status Field

When setting field properties, do not select the options to hide the Status field. Hiding an item that contains the TR_Item_State tag can cause the Action button to disappear from the Defect form.

Team Member Association

In the default schema, "Team Member" is a special type that identifies a user and is associated with the TR_User tag. Although you may create a child type of Team Member, do not attempt to create a child of the child type of Team Member. Doing so will cause unexpected results.

This is an example of a correct association:

Team Member
Manager
Read-only user

This is an example of an incorrect association:

Team Member
Manager

QAManager (Unexpected results will occur)

Read-only user

Deleting Multiple 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 originally created. 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.

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.

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. For example, you may want to enter VCS Project.
  6. Click the Properties tab.
  7. Select VCS project/dir.
  8. Click OK. The new field will appear in the Type Editor.
  9. Click the Save and Close button to exit the Type Editor.
  10. 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.

Miscellaneous

Deleting Defects Using the Item Browser With Read-Only Permission

Guest users have Read-Only permission by default, but are still able to delete defects using the Item Browser. One workaround is to put a hidden field (checkbox) that is only accessible by the admin user.

Exporting Multi-Item List Fields to an Access Database

When exporting to an Access Database, Multi Item List field produce the following error: "Run-time error '3163 The field is too small to accept the amount of data you attempted to add."  Insert or paste less data to work around this issue.

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.

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.

Cut/Copy/Paste Actions

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

Importing Duplicate Items

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

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.

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
One Campus Martius
Detroit, MI 48226

 

End of TrackRecord Release Notes
©2004 Compuware Corporation. All rights reserved. Unpublished rights reserved under the Copyright Laws of the United States.