- Caliber integrations for TCC 6.1: as far as I know, TCC 6.1 can integrate
with Caliber5.1. Caliber 6.* - 2005 plugins included in TCC 6.2 - TA 1.1 can
be incompatible with TCC 6.1
- requirement description: possible in principle - you can write helper
classes using TCC & Caliber APIs and call these classes from your templates
(e.g. using invokeForName() GenDoc function).
- get currently iterated RwiElement using context.getRwiElement() (see
invokeForName() description)
- get its "CaliberReqName" or "__req" properties(depending on Caliber plugin
version, tag names/values are different)
- parse these properties to get the requirement ID (can be done using
com.togethersoft.modules.caliberrm.util.CaliberClientTag methods, e.g.:
let String reqName is a __req property value. Then
String id = CaliberClientTag.parse(reqName).getReqId(); // id here is
requirement ID
you will then need to convert it to Integer
)
- using Caliber SDK API create a new Caliber server connection, get a
requirement by reqId, then get a description via
requirement.getDescription().getText()
Note: in latest Caliber versions getText() returns a description as a String
in HTML format, so when using invokeForName() you'll get an output with lots
of HTML tags - will look ugly in RTF format. I'd suggest generating docs in
HTML format to get the description formatted properly
"Star" <st...@unislabs.com> wrote in message
news:430c3047$1...@newsgroups.borland.com...