CaliberRM® 2008 - Borland Technical Publications

Resolved Issues for 2006
The following table identifies issues that have been resolved in CaliberRM 2006 WW release.
Hot Fix
Hot Fix 16
Hot Fix 17
Hot Fix 18
Hot Fix 18
Hot Fix 18
Hot Fix 19, 20
Hot Fix 20
Hot Fix 22, 22c
Hot Fix 24
Hot Fix 24
Hot Fix 25
Hot Fix 26
Hot Fix 27c
Hot Fix 28c
Hot Fix 29c
Hot Fix 31c
Hot Fix 32c
Change Request Number
40728
40811
23417
23399
22479
40929
22479
41205
40538
40538
40811
40538
41457
41326
41487
41502
41577
Description
CaliberRM CRMDiag Tool not included
in v2008.
CaliberRM CRMDiag Tool not included
in v2008.
CaliberRM SDK application error.
CaliberRM SDK application error.
CaliberRM SDK application error.
Traceability Matrix shows requirements
for projects to which the user does not
have access.
CaliberRM SDK application error.
Datamart Extraction failing.
When a requirement is deleted in 2006,
it appears to be left in a hanging status
but still appears in searches, Document
Factory reports, and stopping-baseline
abilities.
After deleting a requirement, unread
discussions still appear. The owner of
the discussion appears as
?|?.
CaliberRM 2006. Docfactory.exe
version 9.0.906.0.
The Traceability Matrix displays
requirements for projects to which the
user does not have access.
Datamart does not utilize the parameter
-SQLLDR during Oracle extractions.
When importing from Word, a
requirement name is truncated to 64
characters even though the CaliberRM
Client supports requirements with
names of 128 characters.
SCM traces the output ERROR:
Invalid ID instead of the traced-to
object's name in Document Factory.
The usage of the -update parameter
with Oracle results in a failure without
building the database.
The map-requirement functionality
cannot be used with the SDK (applies
CaliberRM 2008 Release Notes | 23