Copyright (c) 2002, Rational
Software Corporation.
All Rights Reserved.
This document contains the following sections:
Information for Word 2002 Users
Contacting Rational Technical Support
This section contains general technical notes for using Rational SoDA for Word.
To access SoDA Help from Microsoft Word, click SoDA > Help on SoDA.
This release of Rational SoDA for Word has unresolved defects. This section lists these known defects, and, if available, the workarounds for them.
If you
experience problems with SoDA for Word, consult the following list before you
call technical support. If you
encounter a problem that is not listed, contact Rational
Technical Support for assistance.
|
Change Request ID: |
RATLC00009488 |
|
Description: |
If you use SoDA for Word with a non-English version of Microsoft Word, you cannot selectively retrieve Headings from the Word domain. |
|
Workaround: |
In the source code for the document template, "Headings" is implemented as paragraph where Style LIKE "Heading". In the template, use a REPEAT on Paragraphs and use the Advanced key to add the following And Where statement: <Self>.Style LIKE "<non-English word for Heading>" |
|
Change Request ID: |
RATLC00016147 |
|
Description: |
If Rational RequisitePro Integration with Word is installed on your machine, and you have never started Word on the machine, SoDA for Word does not start correctly. |
|
Workaround: |
On a machine on which Word has never been started: 1. Start and then quit Word. 2. Start SoDA for Word. 3. Start RequisitePro and then open a RequisitePro project. 4. Click Tools > Generate SoDA Report. The SoDA for Word dialog box is displayed normally. |
|
Change Request ID: |
RATLC00019981 |
|
Description: |
The built-in template “Data Dictionary of Classes with Attributes and Operations” (ClassesAttrsOps.doc) is not available through Rose RealTime. If you start Rose RealTime, open a sample Rose RealTime model, and then click Report > SoDA Report, the Generate Rose RealTime Report dialog box does not list the built-in template. |
|
Workaround: |
To work around this problem: 1. In Windows Explorer, navigate to the following folder: Program Files\Rational\SoDAWord\template\rose 2. Right-click the ClassesAttrsOps.doc file, and then click Properties on the shortcut menu. 3. On the Summary tab, in the Value column next to the Keywords property, delete SoDA Template. 4. Click OK. |
|
Change Request ID: |
RATLC00020353 |
|
Description: |
If you start Template Builder and click ProjectConsole > Template View, and you then start SoDA for Word and click SoDA > Template View, the Template Builder Template View dialog box is displayed. |
|
Workaround: |
Quit Template Builder before you use SoDA for Word. |
|
Change Request ID: |
None |
|
Description: |
If you open Help for SoDA in Internet Explorer 6.0 and display the Table of Contents, you may see an error message about not being able to move the focus to a control. |
|
Workaround: |
To use the Help system without further interruption, close the message box by clicking either OK or No (depending on your environment). |
|
Change Request ID: |
RATLC00026657 |
|
Description: |
To report on IUCM data, SoDA must traverse from ReqPro to Rose via a calculated OPEN. However, SoDA is unable to decipher the OPEN path when coming from ReqPro. |
|
Workaround: |
Hardcode the Rose_Model OPEN command to point to the model. |
|
Change Request ID: |
RATLC00027119 |
|
Description: |
Messages are truncated on sequence diagrams. |
|
Workaround: |
In Rose, display the affected diagram and click Format > Autosize All. |
|
Change Request ID: |
RATLC00031006 |
|
Description: |
If you install XDE 1.1, the XDE domain becomes available when you create SoDA templates. However, the XDE domain is not supported in this release of SoDA. |
|
Workaround: |
None; do not use the XDE domain. |
|
Change Request ID: |
RATLC00031060 |
|
Description: |
A SoDA template that is designed to read custom properties scripted in Rose does not read those properties consistently. |
|
Workaround: |
Before running this kind of report, save the Rose model, close Word, reopen Word, then generate the report. |
|
Change Request ID: |
RATLC00031092 |
|
Description: |
To produce a generated document, a recursive REPEAT command executes the next consecutive DISPLAY command one more time than expected. This results in an additional heading level entry with the DISPLAY command itself as this heading level entry. |
|
Workaround: |
Use the Generate Report command with templates that have this structure. |
|
Change Request ID: |
RATLC00031223 |
|
Description: |
You cannot browse to a ClearCase folder in an OPEN command |
|
Workaround: |
Type the folder name. |
|
Change Request ID: |
RATLC00031230 |
|
Description: |
In some SoDA installations, the SoDA shortcut does not work. |
|
Workaround: |
Use a method other than the shortcut to open SoDA. |
Information for Word 2002 Users
SoDA uses the Word comment feature to store the arguments it needs to extract and display information in a SoDA report.
Because comments have a different appearance and different behavior in Word 2002 than they do in Word 2000, you interact with the comment feature differently in the two versions of Word.
The SoDA Help does not include Word 2002 procedures. Therefore, if you are going to use Word 2002 with SoDA, review the Word 2002 information in Rational’s Solutions Knowledge Base to get this information:
· Comparison of the comment feature in Word 2000 and Word 2002
· Explanation of how to delete Word comments using the SoDA interface
· Procedure for deleting Word 2000 comments from a Word document
· Description of what you do to delete a Word 2002 comment marker in the SoDA context.
Contacting Rational Technical Support
If you have questions about installing, using, or maintaining this product, contact Rational Technical Support using the following email address:
support@rational.com
When you contact Rational Technical Support, please be prepared to supply the following information:
· Your name, company name, telephone number, and e-mail address
· Your operating system, version number, and any service packs or patches you have applied
· Browser you are using
· Suite product name and release number
· Your case ID number (if you are following up on a previously reported problem)