Obtaining
the Latest Release Notes
System
Requirements
What's
New
Technical
Notes
Known
Issues
Contacting
Compuware Customer Support
If you accessed this document from the product media 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. The first time you access FrontLine, you are required to register and obtain a password. 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.
Pentium 4-class processor equivalent or higher recommended
512 MB of RAM (minimum)
250 MB of available hard disk space
Microsoft Windows 2000, XP, 2003, 2000 Server, 2003 Server, or Vista
Adobe Acrobat Reader for Optimal Trace™ Server Help Files
MySQL Version 4.1 or 5.0 or
Oracle 9i Release 2, 10g Release 2, or 11g Release 1, or
Microsoft SQL Server 2000 (SP4), Microsoft SQL Server 2005
Note: There is a known issue with MySQL version 5.0.37 with 5.0.42, which should be resolved for future MySQL releases.
Optimal Trace 5.1 is a fully internationalized release. The product supports American, EMEA, APAC, and other foreign markets. In the APAC market, Japanese, traditional and simplified Chinese, and Korean languages are supported along with English-speaking countries. Additionally, Optimal Trace is UTF-8 Unicode safe, which means user visible strings are ready for translation and runtime functionality supports non-English locales. The following exceptions to internationalization apply:
Optimal Trace offers support for Windows Vista Business, Ultimate, and Enterprise editions. Optimal Trace does not support Basic or Home editions. Optimal Trace runs with Windows Vista's Virtualization Mode set to Off.
Optimal Trace now offers support for Oracle 11g release 1 (11.1.0.6.0). If upgrading to this version of Oracle, manually migrate your database.
Optimal Trace has the ability to ignore custom property errors that arise during document generation. These errors occur when custom properties in the template level and the document level do not match. In previous releases, document generation stopped when it encountered errors. In this release, users have the option to ignore the errors in order to proceed with the documentation generation process. Users can then view the errors and trace their location to the corresponding table. An empty token appears in the document where the error occurred.
Optimal Trace retains column widths within both Simple and Structured requirements and between packages. Users can now easily navigate between requirements and packages assured that their width changes will remain intact.
Optimal Trace provides a new HTML report to its report lineup. The Tree View Report outputs your project with requirements and packages nested in a tree. The actors, glossary, notes, links, NFRs, and details are accessible through links on the left side of the report.
The Project Name, Project Creator, Project Created On Date, and Project Last Modified Date display when opening a project. Users can sort these columns to ease their search for specific projects. Additionally, when hovering over a specific project, the project description displays.
This section includes technical information that may affect how you use the product.
There are no technical notes for this release.
This section describes known issues related to the current release of Optimal Trace.
The following are changes to the Optimal Trace Installation and Configuration guide:
In sections 10.2, 11.2, 12.2, the documentation mentions that the password for the OptimalTrace user is password. The correct password is otpassword.
In section 11.2, one of the bullet points for the UTF Oracle settings lists AL32UTF8. It should be UTF8. The bullet point should read:
Click the Select from the list of character sets button, and then choose the UTF8-Unicode 3.0 Universal Character Set
| Control # | Description |
| 6837 |
Searching the Repository on MSSQLServer seems very memory intensive: Searching data in MSSQLServer 2000 uses up a lot of memory and can cause MSSQLServer to crash. Workaround: You can disable users searching the repository on MSSQLServer by setting the 'allowSQLServerReposSearch' to 'false' in server.properties. Stop and restart the Optimal Trace Server for this setting to take effect. |
Compuware Customer Support can assist you with all your technical problems, from installation to troubleshooting.
Prior to contacting customer support, gather the following information:
800.538.7822
Refer to Compuware's Frontline support web site for fast access to critical information about your QACenter 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.
Refer to Compuware's corporate web site at http://www.compuware.com/ for information about Compuware customer support policies and problem resolution process.
Customer Support
Compuware Corporation
One Campus Martius
Detroit,
MI 48226-5099
End of Optimal Trace Release Notes
(C) 2008
Compuware Corporation. All rights reserved. Unpublished rights reserved under
the Copyright Laws of the United States.