For assistance with product usability issues please follow these steps:
- The product documentation
- The product's built-in Help topics
- Any ReadMe or technical notes provided with the product
- Our online searchable knowledge base (login required)
Call Logging Process
By logging a Support Call, you have access to qualified engineers who can help determine the nature of the problem and provide solutions to your issues. When submitting an issue, you can use any of the following methods. To expedite the process, please follow these steps:
- Log a call to Customer Support . For a high-priority issue, please contact your support center by phone.
- When logging an issue, please provide the following information:
- Company name
- Company client number (issued to you by Compuware)
- Contact person’s name
- Phone number
- Fax number
- E-mail address
- Description of the problem, including error messages
- Steps to reproduce the problem
- Product version number, edition and service pack level
- Client and Server Operating systems (include name and version)
- Database name, version and edition
- MS Word edition
- JDK version
- Integration Product Version and Edition
- Problem priority level (see below for description)
Call Resolution Process
When an analyst receives your issue, a unique call tracking number is assigned. This number will be used to keep track of all exchanges and activities regarding your issue. The issue gets assigned or directed to a specialist on the product in question.
To help expedite the response and investigation process, you should always include your call tracking number with any submission.
Your call will be dispatched to the appropriate expert in one of the following areas:
- Optimal Trace Support Technical Issues:
Once the call tracking number has been assigned, you can communicate with the assigned support analyst using OptimalTrace.Support@compuware.com mailing address. The assigned expert will work with you to recreate and solve the problem.
- License administration and contracts
For license specific questions, you can also visit the Licensing Page (login required)
Description of Priority Levels
When logging a call, you will be asked to assign a priority number to your issue. The following table provides a guideline to help you assign a priority to your issue.
| Priority |
Response Time |
Description |
1 (Critical Problem)
|
1 business hour
|
- No known workaround or solution to the problem at the time the call is logged
- Causes the software or operating system to fail completely
- Requires constant restarting of the software or operating system
- Results in corruption or loss of data
- Prevents the installation of the software
|
2 (Major Problem)
|
4 business hours |
- No known workaround or solution to the problem at the time the call is logged
- Prevents the use of an explicitly documented major function of the software
- Causes a software or OS crash
- Use of the software is seriously impacted (mission critical usability problems)
- Installation issues
|
3 (Normal Problem)
|
8 business hours
|
- It does not meet the criteria of a priority 1 or priority 2
- Product does not work as explicitly documented
- Non-mission critical usability issues
|
4 (Minor Problem)
|
2 business days |
- It does not meet the criteria of previous priorities
- Low priority requests for information (e.g. what is the most current release?)
- Documentation errors
| |
 |