Database Reference
In-Depth Information
whenever the Change event is fired and P3_FROM is not null. In the last step, you
chose P3_BODY as the affected element. This indicates that it's P3_BODY that is en-
abled and disabled depending on the state of the P3_FROM item.
Now, run page 3. Note that the Body item is disabled until you enter something in
the From item and navigate away. Conversely, if you delete all content from the From
item, the Body item again becomes disabled, but only after you navigate away from
P3_FROM . This is OK, but it would be nicer if the Body item became enabled as soon
as you typed anything in the From item. Once a dynamic action is created, you can edit
its properties and access many more options that weren't available in the wizard. Let's
set the triggering event to be Key Release instead of the default Change event. Here's
what to do:
1. Edit Page 3 of the application.
In Figure 16-6 , you see two dynamic actions with the same name. This is actually
the same dynamic action; it's shown in two places purely for the sake of convenience.
Any dynamic action that is tied to a specific element for its triggering event is listed
under the item. At the bottom of the tree, all dynamic actions on the page are listed
even if they don't reference a specific item.
Figure 16-6. Dynamic actions in the Page Rendering tree
 
 
Search WWH ::




Custom Search