Databases Reference
In-Depth Information
Figure 7-81.
Page Rendering section of the Ticket Statuses chart
In APEX 4.2 chart regions, there is no longer a Source section in the region definition. The source that drives the
data is actually contained within the Chart Series on the Chart Attributes tab.
Summary
You've reviewed most of the APEX forms and reports types, and you've walked through building various forms and
reports for the Help Desk system using the APEX form and report wizards. You created an interactive report and
made adjustments as a developer and an end user. You've been introduced to charts, and you added a chart to the
application to visualize your ticket status.
The common theme is that the APEX form and report wizards are huge time-savers for developers, creating all
the objects—items, buttons, branches, processes, and so on—needed for a working form, report, calendar, or chart.
You were able to alter the created objects to quickly customize the generated form or report to suit your needs. Still,
you haven't strayed far from what APEX builds for you.
As your application becomes more complex, there will be places where you wish to add code to enforce
business rules or perform more complex processing logic than a simple insert, update, or delete. To do so, you can
use the various programmatic elements of APEX. The next chapter addresses the topics of validations, computations,
and processes.
