Under the Property Editor, select the Visibility tab. Check Hide Element.
20. Use the Expression as illustrated in the following figure:
21. Select the bug_id data element.
22. Under the Property Editor, select the Hyperlink tab.
23. Create a Drill-through to the BugzillaDetailreport.rptdesign using the
Table's bug_id as the parameter value.
Chapter 12
[ 289 ]
24. Apply the TableHeader Style to the report.
25. As we used the Visible Expression to hide rows that are resolved, this will
throw the Highlight used in the Detail Row style off. So, we are going to use
a little bit of Scripting to apply our Highlight. Open up the Outline view.
26. In the Report Designer, open up the Script tab.
27. Select the report's Root element, and in the Script editor, choose the
initialize method.
28. Use the following code:
29. Select the Detail Row in the Report Designer.
30. For the onRender method, put in the following code:
31. In the Property Editor, select the Highlight tab.
Practical Example??”Building Reports for Bugzilla
[ 290 ]
32. Create a Highlight using displayedRow % 2 instead of row.__rownum.
33. Save and Preview the report.
The reason this worked is because we needed to get the values in the data rows
before the visibility rule takes effect. Once we have those components created, we
check in the Render phase to see if the value of bug_status is the RESOLVED value.
Pages:
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230