CaliberRM® 2008 - Borland Technical Publications
CaliberRM® 2008 - Borland Technical Publications
CaliberRM® 2008 - Borland Technical Publications
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
When you use the CaliberRM SDK to create a user, the User Can Manage Glossary Terms permission<br />
is enabled by default. No SDK option exists to deselect this permission. However, if this permission needs to<br />
be disabled, you can disable it on the Security page of the CaliberRM Administrator.<br />
Do not use surrogate pair characters, which the CaliberRM SDK does not support surrogate. Clients that use<br />
the SDK cannot process surrogate pair characters appropriately.<br />
If you do not have the corresponding OLE object software installed, the Edit object command, without<br />
warning, does not open the OLE object software.<br />
The Export to MS Access function does not include StarTeam traces. Use the Datamart extractor to MS Access.<br />
Mercury QC traces are not exported to MS Access when you choose File ➤ Export to Access. Consequently,<br />
you must log on to QC before initiating the Export to Access function.<br />
Traces to deleted requirements are displayed as Retrieving on the Traceability page.<br />
Rows and columns in the Traceability Matrix cannot display non-requirement objects without displaying some<br />
requirements. To avoid this issue, use ID equals as a filter criteria to display one<br />
requirement along with the external objects.<br />
Saved traceability matrices do not persist the traceability matrix layout or the user filter.<br />
In user baselines, the message Retrieving... is displayed instead of the trace to requirement deleted in<br />
current baseline.<br />
Due to the versioning of traces, creating some baselines might take longer in the current version than in<br />
CaliberRM 2005.<br />
Traceability cannot be included when pasting requirements after a copy. Instead, use the Paste Special<br />
functionality.<br />
Document Factory<br />
Due to a localization issue, the Document Factory's logging directory is changed from C:\Documents and<br />
settings\Local Settings\Application Data\<strong>Borland</strong>\CaliberRM\Log to C:\Documents and<br />
settings\\Local Settings\Application Data\<strong>Borland</strong> Software<br />
Corporation\<strong>Borland</strong>\CaliberRM\Log.<br />
If you are generating Document Factory with requirement trace-to-SCTM linking service, the external trace<br />
does not appear in the document.<br />
When running a previous version of Document Factory (with MS office 2000), you must click the Multiple<br />
option instead of Once to replace the keywords properly for all the records.<br />
In new Documentation Factory for versions 2003 and 2007, an Invalid Query message appears during<br />
document generation when the $filter command, which contains the old Document Factory syntax, is used<br />
in the template.To avoid this message, create and save a new filter on the server, and then modify the $filter<br />
tag with new filter criteria.<br />
The new Documentation Factory for versions 2003 and 2007 does not support filtering in SQL format.<br />
Consequently, you must create and save a new filter on the server, and then modify the $filter tag with<br />
new filter criteria.<br />
The Document Factory option in the Requirements Grid is not available when the grid displays a single<br />
requirement. To make this option available, display the grid with multiple requirements and manually select<br />
the requirement.<br />
The current baseline is specified with $BASELINE{Current Baseline} instead of $BASELINE{Current}.<br />
28 | CaliberRM <strong>2008</strong> Release Notes