Developing Report Actions
This chapter contains the following sections:
reports, you can also include actions to go with those reports.
Developing a report
action requires the following things:
This structure is
similar to workflow tasks because workflows use the same framework. The
difference is that your handler will extend from a different class.
The form object is a
POJO with JDO and FormField annotations. It should look very similar to the
config objects that you developed for your workflow tasks. The only difference
is that there is no need to implement any interface. You might want to use the
JDO annotations if the form has data that you want persisted; they make it
easier to retrieve and persist the POJO from the database. Use the FormField
annotations to specify which user interface (UI) control to display to the
You should place the
logic for your report action in a handler. The handler extends
The form handler
includes several methods that you might want to override:
definePage—Defines the layout of the form. You want to
bind your form object to the page, and the UI will generate a form as defined
by your form object.
loadDataToPage—Handles loading data that you might
want to show in the form when it is first displayed to the user.
validatePageData—Handles whatever logic that you want
to execute when the user presses the submit button.
For examples of the
form object and the form handler, see the
in the sample code.
After completing the
development of actions, you must associate them with a report, such as a report
To associate them with a report, you must implement a
getActions method and provide instances of your