If
not, then we advance the counter that would normally be advanced by ROWNUM.
This keeps it nice and uniform.
Chapter 12
[ 291 ]
Summary
In this chapter, we looked at a realistic example of a series of reports that could be
used in a real-life project. In fact, these requirements were based on some examples
of report requirements I have been given in the past.
We illustrated just about every major element of reporting with BIRT??”Report
Project, Report Components, Charts, Scripting, and Formatting. We even looked
at how to look at requirements and find reports with similar specs and data and
combine reports. If a single report can take the place of multiple reports, and tell a
more complete story, it is always beneficial to do so. In addition, we also introduced
the Visibility rule, which is very similar to the Highlight rule. These reports can now
be deployed to a report platform and be used for production reports.
Keep in mind that these reports were created in a controlled environment.
Many times, data won't be as clean. For example, I based my assumption for the
Developer Performance Report on the fact that there would only be two classes of
statuses??”open and closed. In reality, Bugzilla keeps this open-ended, and there are
Open, Resolved, Assigned, and a few others out of the box.
Pages:
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231