Databases Reference
In-Depth Information
Type
: The type of plug-in that you're building; there are six different types of
plug-ins: authentication, authorization, dynamic action, item, region, and
process. Plug-ins can be run as part of the render, validation, or page process.
Table 2-1shows how each type of plug-in can be used in an APEX page. Once a
plug-in has been used in an application, the type cannot be changed. The type
cannot be changed because each plug-in type has a distinct set of attributes
that will become evident in the Callbacks section.
The plug-in type determines when, and how, the plug-in will be used, as shown in Table 2-1. Plug-
ins that can be rendered usually (except for authorization types) require HTML code to be sent to the
browser. Validation executions happen once the page is submitted. Processes can happen while the
page is being rendered or when the page is submitted.
Table 2-1. Plug-In Execution Options
Type
Render
Validation
Process
Comments
Authentication schemes are used to determine if
the user can access the application. As such it is
not run on a page or component level.
No
No
No
Authentication
Authorization schemes can be executed for all
APEX objects on a page. They don't actually
render, validate, or process anything in the
application.
Yes
Yes
Yes
Authorization
Since dynamic actions are only valid for the display portion of
APEX they are only available during the render process
Yes
No
No
Dynamic action
Starting in APEX 4.0, page items may contain
built-in validations that APEX developers don't
need to explicitly define.
Yes
Yes
No
Item
Process plug-ins can be run as a page render
process and page process. Usually it will be used
as part of a page process.
Yes
No
Yes
Process
Similar to dynamic actions, regions are only valid
for the display portion of an APEX page and thus
are only available during the render process.
Yes
No
No
Region
