Field dependency, reporting, and auditing hooks

	Field Dependencies
	Auditing
	Reporting

Sample hooks for users of IBM® Rational® ClearQuest®

These items were originally published in 2003 and may refer to earlier versions of Rational ClearQuest.

NOTE: These hooks are presented only as examples of how to customize your use of IBM Rational ClearQuest. They have not been formally tested and are not supported by IBM.

Scripts that are used to manage dependencies between multiple fields in a ClearQuest record type. This includes dependent choice lists and constraints that may exist between different fields:

• Field-dependent choice list
  
  
• Value changed hook -- through SQL
  
  
• Dependent field choice lists using SQL
  
  
• User fullname drop-down list
  
  
• Clone a defect
  
  
• Dynamically create dependant choice lists for fields
  
  
• Multiple ways to enter/see user references

Back to top

Scripts that are used to audit ClearQuest actions more completely:

• Field level auditing
  
  
• Getting the last line in the history tab
  
  
• Logging field changes for historical purposes
  
  
• Track all changes to records including field changes
  
  
• A full field auditing script that tracks any change to any field
  
  
• Track changes to a record in an Update_Log field
  
  
• Append message to Field_History record when a field changes
  
  
• History of field changes
  
  
• Record user name of changes to a field of a record in a certain state

Back to top

Scripts that are used to automate ClearQuest reports using Microsoft Word or other systems:

• Get reference list and attachment info for reports
  
  
• Microsoft Word doc from within IBM Rational ClearQuest
  
  
• How to use the ChartMgr object
  
  
• How to execute an existing report using the API
  
  
• External VB application to do something with records not touched in 14 days
  
  
• A VB application that generates IBM Rational ClearQuest reports and charts and more
  
  
• Create an IBM Rational ClearQuest aging report and chart
  
  
• Output length in days that records have been in a particular state
  
  
• Leverage Microsoft Word as an editable report template and report generator
  
  
• Create a query in the user database using external API
  
  
• ChartMgr example with CQPerl

Back to top