Database Reference
In-Depth Information
logy to do so. In fact, it's likely that you could code upward of 80% of everything you
need to do with nothing more than the Dynamic Action Wizard and SQL and PL/SQL.
However, because JavaScript is the de facto standard for coding browser interactiv-
ity, it's also likely that at some point you'll be forced to learn a bit about JavaScript.
Learning JavaScript is beyond the scope of this topic. After all, you bought this topic to
learn APEX. But if you do want to learn more about JavaScript, Apress has a number
of excellent topics on the topic.
Breaking Down Dynamic Actions
Prior to APEX 4.2, dynamic actions were split into two categories: Standard and Ad-
vanced. The only real difference between these two categories was what the related
wizard let you achieve. Under the covers, both dynamic action types were identical;
and once you left the wizard, all options were available to you. APEX 4.2 has done
away with this artificial separation and now provides only one wizard to create dynam-
ic actions.
The definition of a dynamic action can be broken down into the following compon-
ents:
Identification
: Defines the name of the dynamic action and its execution
sequence.
When
: Defines when the action will be fired. You can choose the event,
the object or objects that will participate in causing the action to fire, and
any condition that applies to the event.
Actions
: Dynamic actions can contain both True and False action sets.
The True action set is executed if the defined event occurs for the se-
lected objects and any condition applied evaluates to
TRUE
. The False
action set executes if the defined event occurs for the selected objects
and any condition applied evaluates to
FALSE
.
Affected elements
: Identifies which objects on the page are affected by
the dynamic action.
As with other parts of APEX, dynamic actions support conditions, authorizations,
and build-option features.
