User's Guide > About the User's Guide > Word and Excel Templates > Word Templates in CB 7.1 and Older > List of Objects/Entities Available in the Export Context
List of Objects/Entities Available in the Export Context
This table lists the objects available in the velocity script above:
variable name
type
description
baseline
com.intland.codebeamer.persistence.util.Baseline
The current baseline object if any (can be null).
request
HttpServletRequest
The http request being processed.
user
com.intland.codebeamer.persistence.dto.UserDto
The requesting Codebeamer user.
currentDate
java.util.Date
Current date-timestamp.
project
com.intland.codebeamer.persistence.dto.ProjectDto
The current project where the tracker being exported is.
requirementTracker
com.intland.codebeamer.persistence.dto.TrackerDto
The requirement tracker.
requirements
SortedMap<ReleaseId,TrackerItemDto>
Requirements as TrackerItemDtos grouped by release-ids.
incomingReferencesByIssue, outgoingReferencesByIssue
Map<Integer, Map<String, List<IdentifiableDto>>>
Map contains for each requirement's id the incoming or outgoing associations from/to that requirement. Important: these are not the referenced issues via reference fields, but the associations between other issues in the system.
About figuring out what properties are available on of these Codebeamer objects: please look at the remote-api documentation and the javadoc found in. As you may already know Codebeamer provides a rich API for querying and manipulating Codebeamer objects programmatically using an RPC protocol. This API is documented here:
So the remote-api contains the Javadoc of most internal Codebeamer objects I've listed above, and is shipped with the Codebeamer distribution. You can find it below your Codebeamer installation directory on a path like: $CB_HOME/tomcat/webapps/cb/codebeamer-api-6.0.0.zip. If you unzip this zip file somewhere then you will see a "docs/api/" directory where the generated Javadoc resides. Open the index.html here and you will find the Javadoc and properties of the objects (like our TrackerItemDto).
Be warned however that the signature of these objects, the export scripts may and practically will change between any new Codebeamer releases in the future. I would strongly recommend that you try to keep your customizations as isolated as possible, and using a git repository for tracking such changes is recommended. This will make your life much easier if you plan to upgrade Codebeamer in the future.
Was this helpful?