|
1686
|
- Inconsistent error message when cancelling word
document generation and Word may crash
Depending on when you interrupt the document
generation process, you may receive a COM exception returned from Microsoft
Word and Word may crash.
Workaround: Ignore the exception from Microsoft
Word, Optimal Trace Enterprise continues as normal. You may additionally need
to stop the winword.exe process in Task Manager.
|
|
2147
|
- Document generation and form protected style
template
When using a Microsoft form document as a style
template for a document generation profile, Optimal Trace will not generate the
document if the form is protected..
Workaround: Do not protect the style template
form before generating.
|
|
2172
|
- Links don't work in generated document
If generating a form-based profile (e.g. Default
Form), links in the document (e.g. Table of Contents, hyperlinks, etc) do not
work.
Workaround: This is a known feature of Word
forms. These links will not work if the document is protected. To allow working
links, do not protect the form. Deselect the Protect Form toolbar
button.
|
|
2267
|
- Incorrect macro security settings in Word can lead
to application error
If generating a document from Optimal Trace and
an exception occurs, ensure that the security settings in Word are set to
Low.
Workaround: In Word, ensure that the macro
security option is set to Low. For example, in Word 2003, choose
Tools>Macro>Security Settings. The Security Settings dialog box appears.
Ensure that the option is set to Low.
|
|
2354
|
- Change History changes do not get included as part
of a document update
Optimal Trace was designed to not include any
Change History additions as part of a document update if that profile has a
Change History element.
Workaround: Generate either a standalone Change
History document or re-generate your document from scratch to see all the
Change History entries.
|
|
2501
|
- Out of Memory Errors while generating HTML or Image
Maps from large Projects
Generating Image Maps from large Projects is
very memory intensive. If you repeatedly generate the 'Full Project' HTML
Report with a large Project you will eventually get an Out of Memory Error. The
same can happen if you repeatedly 'Save Image' for a very large Project.
Workaround: Try and limit generating HTML for
large Projects or Image Saving to once per Optimal Trace session. If you do get
an Out of Memory error, restart Optimal Trace and re-try generating HTML or
Save Image once again.
|
|
3301
|
- Timestamps on merging a reversed document
When reversing a document, the timestamp of all
merge changes are taken from the document, even if the application has changed
in the meantime (i.e. if the project in Optimal Trace is newer than the
document).
Workaround: There is currently no workaround for
this.
|
|
3558
|
- System clocks between Enterprise Server and
Enterprise Clients need to be manually synchronized:
If you notice a significant disparity in the
timestamps of certain Project objects while using the Merge tool in
online/offline scenarios, please ensure the system clock on the machine with
the Enterprise Server has the same time as the system clock on the Enterprise
Client machines.
Workaround: Currently these system times need to
be maintained manually.
|
|
4031
|
- Orphaned Branch or Refinement in the Requirements
Map
In certain rare situations a line representing a
Branch or Refinement may get duplicated resulting in an orphaned line remaining
on the graph. This line has no connection to any Requirements or Steps and as
such will not result in any errors or corruption of projects, but may prove an
annoyance.
Workaround: You need to open a new window
(Window -> New Window) and close the original window and continue as
normal.
|
|
4241
|
- Cannot add form fields to non-form document
profiles
If you attempt to add form fields to a non-form
document profile, Optimal Trace may not be able to reverse or update the
profile.
Workaround: Avoid using form fields in non-form
based profiles. It's perfectly ok to add custom fields to form based profiles,
but just don't mix the two.
|
|
4287
|
- Table of contents page numbers can be
incorrect
After updating or reversing a document, you may
notice that the page numbers in the table of contents to not correlate
correctly to the document content.
Workaround: This behavior seems to be related to
the large amount of hidden text that Optimal Trace documents contain. Removing
all the hidden text can help here (but you will no longer be able to update or
reverse the document). See the Document Generation: General Tips section below
for details on how to remove all the hidden text in a document.
|
|
4427
|
- Document Generation will fail if you use 'xxxxx' as
a Requirement name
'xxxxx' is a reserved word used internally by
Optimal Trace document generation, and if you use it as a Requirement name in
your Project, document generation will fail.
Workaround: Avoid using 'xxxxx' as a Requirement
name.
|
|
4672
|
- Type of images generated during Report
generation
It should be noted that the style of images
generated during Report generation (using the 'Default HTML' report for
example) all depend on what 'graph display option' is selected in the
application.
Workaround: You can vary the images by right
clicking on the Requirement Map and changing the Package display style.
|
|
4735
|
- Cannot update or reverse documents after Repository
Save As
When you use the Repository 'Save As'
functionality, this creates a new Project in the repository. Hence, you cannot
reverse an existing document (or perform an update) using this Project.
Workaround: none.
|
|
4757
|
- 'Hide Steps' option can cause instability when
moving Steps
Under certain circumstances, using the 'Hide
Steps' Requirement option along with moving Steps can cause Optimal Trace to
crash.
Workaround: try and avoid using the 'Hide Step'
Requirement options.
|
|
4859
|
- Saving Change History and DocGen logs locally
When downloading a remote project to a local
project, Optimal Trace also downloads the project's change history and docgen
events. For projects with many changes, the change history and docgen events
can comprise of data which is a couple of times larger than the project itself.
This, obviously, affects the time it takes to download a remote project. If the
change history and/or the docgen events are not needed locally, then the user
may instruct Optimal Trace not to download these items. Note, when uploading
and merging a local project to a remote project, the local change history and
the local docgen events are not used - the merge tool generates change history
items and docgen events corresponding to the merge result.
Workaround: To disable the download of change
history and docgen events, follow the steps below:
Exit Optimal Trace
Open the file 'default.properties' in a text
editor (e.g. Notepad). The file is located in the Optimal Trace directory (e.g.
C:\Program Files\Optimal Trace\Optimal Trace Enterprise Edition)
Disable download of the change history by
changing the line 'downLoadProjectChangeLogWhenTakingOffline = Yes' to
'downLoadProjectChangeLogWhenTakingOffline = No'
Disable download of the docgen events by
changing the line 'downLoadDocGenEvensWhenTakingOffline = Yes' to
'downLoadDocGenEvensWhenTakingOffline = No'.
Save the 'default.properties' file.
Start Optimal Trace.
|
|
4861
|
- Using the Change History in a Report
By default, the Project Change History is not
passed to the Velocity Report generation engine. This is for performance
reasons.
Workaround: to use the Change History from a new
Report, change the 'passChangeHistoryToReportGenTemplates=No' setting in
'Default.properties' (located in the Optimal Trace installation directory) to
'passChangeHistoryToReportGenTemplates=Yes'.
|
|
4876
|
- Problems with 'Create Reserved Area' menu option in
Word
To begin with, it's recommended to display
hidden text before using this feature (Optimal Trace->Toggle Hidden Tags).
This is because the caret may not be at the correct position, even though it
looks fine without the hidden text on screen. What can happen, for instance, is
that the Reserved Area gets inserted into the middle of another XML tag, which
destroys the document's structure.
Workaround: In any event, most of the time
Reserved Areas are unnecessary, as it is possible to insert text as-is into
almost all areas of the document without needing any "wrapping". Reserved areas
are mainly needed for the characters '<' ,'&', or similar input that
would interfere with the document's XML structure. The best approach is:
Turn on hidden text.
Insert your new content as-is, at the correct
caret position.
Save and close the document.
Try reversing the document into the
corresponding Optimal Trace project. If any XML parse errors are flagged, click
on the error location '...' button and wrap the offending text in a Reserved
section. This will presumably be the new content you have just entered.
If no errors were reported by the import
process, then everything should be fine. You can either cancel or continue the
merge process, as you like.
|
|
4877
|
- Problems with 'Replace IDs and Names' menu option
in Word
Indiscriminate use of this feature can cause
problems and leave the document in an invalid state, so use it with
caution.
Workaround: In any event, most of the time
Reserved Areas are unnecessary, as it is possible to insert text as-is into
almost all areas of the document without needing any "wrapping". Reserved areas
are mainly needed for the characters '<' ,'&', or similar input that
would interfere with the document's XML structure. The best approach is:
Workaround: The following is recommended:
Make a backup of the document before doing
any advanced editing along these lines.
Turn on hidden text.
Carefully select the area that needs
updating. Make sure that any ID strings (usually at the start of a section)
that you wish to update are included in the selection.
. It will help to clarify exactly what
'Replace IDs and Names' does. It updates the IDs and names of any objects it
detects in it's selection. However it does not update the IDs of other objects
that these objects refer to. So for instance, if you copy and paste a
refinement, then selected the newly pasted area and click 'Replace IDs and
Names', this new refinement will receive a fresh name and ID. However, it's
source StepId and destination Requirement ID will not be updated. Therefore
there will be 2 refinements starting from the same step and refining to the
same Requirement, which is illegal. This will show up as an error when this
document is reversed into Optimal Trace. In this and similar situations,
further manual editing of the document is necessary after 'Replace IDs and
Names' has been run.
Replace IDs and Names also corrects the Step
Position numbers on any Step tables it finds. This is a convenience for the
user as manually fixing Step Position numbers can be time-consuming.
|
|
4878
|
- Problems with 'Duplicate current row' menu option
in Word
This menu item will duplicate the current row
the caret is positioned on (e.g. a Step in a Scenario Table). You cannot use
this feature to add a new step to an empty table, there must be one already
there for it to copy. The duplicated item will get a fresh name and ID, and if
it's a Step, any affected Step position numbers will be updated. However it
will not update any other properties of the duplicated object, so sometimes
further manual editing is necessary.
Workaround:
Turn on hidden text and navigate to a branch
table (which is hidden by default).
Place the caret on a particular branch and
select 'Duplicate Current Row'.
Select 'Toggle Hidden Tags' again as this
macro turns off hidden text.
The new branch will have a new name and ID,
but the IDs of it's source and destination Steps will remain the same.
Therefore you now have 2 branches coming from the same Step and branching to
the same Step, which is illegal. This will show up as an error when the
document is reversed.
The new branch will have to manually edited
to correctly contain whatever sourceID and DestinationID are required.
|
|
4984
|
- Problems with manually setting tags to hidden in
Word
If a document is being manually edited and the
editing involves changing hidden text to visible text, or vice-versa, problems
can occur. A typical problem is that even though only one word was changed from
non-hidden to hidden, a large amount of the document surrounding that word
automatically gets changed to hidden text as well. Including important Optimal
Trace data such as the ActorList, for instance. Then, when the editing is
finished and 'Optimal Trace->Toggle Hidden Tags' is selected, the ActorList
will appear to have disappeared, as it is now rendered in hidden text.
The reverse problem can also happen, where a
quantity of previously invisible content suddenly appears. Word is trying to
automatically update the underlying style in that paragraph, rather than just
update the selected text.
Workaround: Firstly, the document should always
be backed up before commencing manual edits, as there are many traps like this.
To get rid of the immediate bad formatting, click undo until the document has
reverted to it's state before the hidden-text edit had started. Now click
Format->Style (or Format->Styles and Formatting depending on your version
of Word). Now select the Style type of the text you were editing. Usually 'Body
Text', 'Hidden', or 'Normal' but it could be any of the other types as well.
The style type of the selected text appears in the Formatting toolbar, which
can be turned on under Tools->Customize->Toolbars. When the correct style
type has been selected, click 'Modify...' and deselect the 'Automatically
Update' checkbox. Now it should be possible to change the text from hidden to
non-hidden in safety. This problem typically occurs when some of the hidden XML
tags in a generated document have been accidentally damaged, and the user is
fixing the errors manually.
|
|
5122
|
- Problem with validating a Skeleton Document that is
already open
If your editing a Skeleton Document in Word, and
you validate it in Optimal Trace (from the Document Settings screen), you risk
losing work as Word does not let you save and continue properly.
Workaround: avoid validating a Skeleton Document
and editing it at the same time.
|
|
5217
|
- Project Elements appear in different order in
Merge
Under certain conditions, the Project child
elements will appear in a different order in the From and To Merge
Projects.
Workaround: There is no workaround; the
appearance order does not effect the underlying functionality.
|
|
5389
|
- Print Preview for Optimal Trace Documents shows
hidden text
Workaround: In Word, ensure that Hidden Text is
unchecked. For example, in Word 2003 go to Tools>Options>Print to view
the setting. For other versions of Word, refer to the Word help within the
Microsoft product.
|
|
5465
|
- Canceling some actions in Optimal Trace does not
release locks
If you do something in a dialog in Optimal Trace
(e.g. move a Requirement) and then cancel the action, the objects in question
will still remain locked by Optimal Trace.
Workaround: Save your project to release the
locks.
|
|
5470
|
- Document Generation Custom Property
restrictions
Custom Properties have to be contained in a
table, they are bound to tables.
Custom Properties are either row-or column
based and again this is statically bound. You can't change your Step Custom
Properties from column type to row type by editing the skeleton doc, for
instance.
Custom Property Template details (name, Id
etc) have to appear before the corresponding Custom Properties in the skeleton
doc. So you can't put your Custom Property name on the right of a row (if it's
row-based), it has to appear to the left.
|
|
5474
|
- Document Generation Profiles cannot contain the
same Element data twice
E.g. in a Document Profile, you cannot have a
Requirement 'Description' repeated twice anywhere in the profile.
Workaround: there is no workaround for
this.
|
|
5535
|
- Document Generation cannot reverse '...' values:
'...' is a reserved word of sorts in reversing a
document, any valid values of '...' will cause invalid conflicts in the Merge
Tool.
Workaround: try avoiding using the value '...' in
your data.
|
|
5549
|
- Can't Auto-Generate a document if any Project
Element has more than 13 Custom Properties
If you attempt to generate a document, where a
Project Element has more than 13 Custom Properties, you will receive the
following error message from Word: "Internal error: Error code: 0x800403e8
Error description: Unable to automatically add and format Custom
Property..."
Workaround: This is a Word restriction, however
it is possible to create a Custom Profile with more than 13 fields.
|
|
5611
|
- No locally locked icons when pasting/redoing
No locally locked icons appear in Optimal Trace
in certain situations, e.g. if you undo a Requirement delete, or if you paste a
Requirement.
Workaround: there is no workaround.
|
|
5689
|
- Searching for individual characters across all
projects can result in a 'Connection Exception'
Searching the whole database for a single
character (or small word) may result in too much search information being
returned from the database to Optimal Trace, and cause a 'Connection Exception'
in the Optimal Trace Client.
|
|
5720
|
- Optimal Trace/Word 2003 update problem
When updating a Word 2003 or Word 2007 document
from Optimal Trace, I get a 'String too long' exception from Word.
Workaround: This is because of a bug in Word 2003
and Word 2007, which is detailed here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;163192. The workaround
is to regenerate your document fully from Optimal Trace when this error
happens, instead of using the Update feature.
|
|
6064
|
- When reversing a document, Package 'Tags' values do
not get reversed
Workaround: there is no workaround, it is not
possible to change Package Tag values in a Word document and reverse them back
into Optimal Trace.
|
|
6235
|
- Hiding paragraph ends in MS Word Templates
Paragraph ends must be hidden in Optimal Trace
MS Word document templates. For example, the section in the skeleton docs
between 'MainSuccessScenario_Template_Start' and
MainSuccessScenario_Template_End' currently ends with
</MainSuccessScenario>¶ which is all hidden. Note the paragraph symbol at
the end. This paragraph character must be made un-hidden in the skeleton,
otherwise Word gets confused when pasting this section into the generated
doc.
Workaround: This appears to be a bug in Word,
there is no workaround, you must keep the paragraph ends visible.
|
|
6613
|
- 'Normal.dot read only' message
After generating a word document from Optimal
Trace, I receive a 'Normal.dot is read only' message when I shutdown MS
Word.
Workaround: This is a problem with Word, to fix
it, run 'Help/Detect and Repair'
|
|
6775
|
- Notification emails do not contain hyperlinks
When I receive an email from Optimal Trace,
there are no hyperlinks to Optimal Trace elements in the email.
Workaround: This is most likely because your
virus checker is stripping out the URI links in the email as it thinks they
might be malicious. To fix this, consult your email Administrator and modify
your virus checker settings.
|
|
6803
|
- Only 500 search results are returned from Optimal
Trace Server, and I was expecting more.
Workaround: This is configurable, to return more
results, edit 'default.properties' in your Optimal Trace Enterprise
installation directory, and set 'reposSearchMaxReturn' to whatever number you
want.
|
|
7001
|
- Merge problem creating the same Custom Property in
both on-line and off-line projects
If you create a customer property 'A' in both an
on-line and off-line project, when you merge those projects Optimal Trace merge
does not merge correctly.
Workaround: Although both Custom Properties have
the same name, internally they are different objects as they were created in
two different versions of the project. Try to avoid creating Custom Properties
with the same name in on-line and off-line projects.
|
|
7073
|
- Uninstall fully removes URI registry keys
If you uninstall Optimal Trace, it fully cleans
up the windows registry. However, if you have a previous installation of
Optimal Trace (or an installation of Optimal Trace Professional), the URI's
will stop working. This is because the newer uninstall would of removed the
'Optimal Trace' URI setting.
Workaround: To re-register the 'Optimal Trace'
URI setting in the registry, it is necessary to re-install the older version of
Optimal Trace.
|
|
7544
|
- Cannot split Custom Properties in Document
Generation
Note that you cannot split up Custom Properties
in a generated document, i.e. you can't have property values spread across
different tables.
Workaround: There is no workaround for this, it
is by design.
|
|
8295
|
- Top of Doc Import Dialog Box hidden under word
menu
Sometimes in Document Import, the Import Dialog
goes "under" the Word menu bar.
Workaround:
Click on the document in word.
Click on the import tool.
Try to keep the import tool away from the
Word menu bar, where it can get 'overlapped'.
|
|
8357
|
- Word changing views in Document Import
Sometimes Word automatically changes a
document's display mode to Normal View, and turns on the Reviewing Pane. This
will appear to the User as though all the Comments have disappeared from the
right hand side of the window, and reappeared in a new Pane on the bottom. As
Word makes this change silently & automatically, based on the current state
of a particular document, it is difficult to intercept and filter out. It does
not seem to happen very often.
Workaround: To change the display back to the
previous settings, the user will need to:
Select View->Print View
Select View->Toolbars->Reviewing to
display the Reviewing Toolbar. On that toolbar, click 'Show' and toggle the
'Reviewing Pane' switch.
|
|
8402
|
- Cannot invoke Doc Import wizard with restricted
permissions
If the user is importing into a remote, secure
project, then they will need full Permissions (modify) for the whole
project.
Workaround:
Take the project offline (this gives full
permissions).
Do the import.
Merge the project back to the repository.
The merge window will take care of any changes to which you do not have remote
Permissions.
|
|
8431
|
- Importing into remote Project
If the user is importing into a remote project,
it is possible for another user to interfere with their import. If the second
user locks and edits something, the first user will be locked out from their
Doc Import Merges. A "project locked" message will be displayed every time,
even if the second user hits Save.
Workaround: There are 2 workarounds: 1) Save your
Word doc, select Close in the OptimalTrace import dialog, then restart the
import. 2) Take the project offline, so you have a local snapshot with no
multi-user locking issues. Import as normal. Then, merge the local project back
to the Repository one.
|
|
8435
|
- Upgrading MySQL from MySQL 4.1 -> MySQL5.0
If your Optimal Trace repository uses MySQL 4.1
and you wish to upgrade to MySQL5.0, you cannot do so directly by just
upgrading MySQL alone, as the Optimal Trace schema will not migrate ok.
Workaround: Do the following: Take all your
Optimal Trace Repository projects off-line while the Optimal Trace Repository
is using MySQL 4.1. Stop the Optimal Trace Server. Install MySQL5.0. Install a
new Optimal Trace database in MySQL5.0 using the MySQL install scripts provided
(see Server Help file for more details). Change your Optimal Trace Server
settings to point to the new database (and restart the Optimal Trace Server).
Upload your off-line projects back into the repository.
|
|
8445
|
- Document Import on Citrix/Terminal Server
When Optimal Trace is installed onto a Citrix
Server, the doc import component will only work for the User who performed the
installation. This is because the install process can only register the Doc
Import dll for the current user. It has no way of knowing about all the other
users, who will connect to the Citrix machine in future.
Workaround: Each of these users must log onto the
Citrix Server as themselves. Then they must follow the instructions provided in
Optimal Trace Help section 3.2, to manually register the dll. The next time
they connect to Citrix (logged in as themselves) and run OT, the Doc Import
component should be working OK.
|
|
8443
|
- Spell Check does not check Custom Property
Templates
Spell Check will only check Custom Property
Templates (i.e. the Custom Property Names, Definition, Default Value, etc) of a
Package if that Package is not shared and there exists an element in that
Package that has contains those custom properties.
Workaround: If you find this happening, create an
element in the parent Package which is not being shared, and run Spell Check
again. This will correct all sub Packages which are sharing with the parent
Package.
|
|
8447
|
- Document Import: problems importing Project 'Owner'
and Package 'Tag' fields
While importing a document, if you mark up the
Project 'Owner' or Package 'Tag' field and that field contains a carriage
return, newline, or tab, your imported Project may become corrupt.
Workaround: try to ensure that your imported
'Owner' field and Package 'Tag' does not contain these characters.
|
|
9433
|
- Error message appears when opening Optimal
Trace
When opening Optimal Trace Enterprise, the
following error message appears: Error in Java launcher. Error occurred while
calling main method in java class
<com/steeltrace/tools/pelican/PelicanApp>. This problem exists in the
Korean and Japanese OS.
Workaround: Elevate user privileges to
Administrator. Right-click either the cmd.exe when running via the command
prompt or the setup.exe of the media browser to change privileges.
|
|
9433
|
- Out of memory error
This error may occur when opening large projects
from the client, starting the server, or when performing administrative
functions.
Workaround: Increase the default heap size option
(-Xmx500M) in the appropriate configuration file. File locations
for each configuration file are as follows:
- Client
<INSTALL_DIR>\Program
Files\Micro Focus\Optimal Trace\Optimal Trace Enterprise Edition\Optimal Trace
Enterprise.lap
<INSTALL_DIR>\Program
Files\Micro Focus\Optimal Trace\Optimal Trace Enterprise Edition\Optimal Trace
Professional.lap
- Server
<INSTALL_DIR>\Program
Files\Micro Focus\Optimal Trace\Optimal Trace Server Edition\ Optimal Trace
Server.lap
- Adminstrator
<INSTALL_DIR>\Program
Files\Micro Focus\Optimal Trace\Optimal Trace Enterprise Edition\Optimal Trace
Admin Tool.lap
The amount of increase in the heap size is dependent on
your environment's memory capacity.
|