About Client Actions

Not all components in ADF UIX support client actions. Client actions are events that are triggered in response to user actions (such as clicking a link or a button) and sent to the server or middle tier for further processing.

The ClientAction API enable supported components to send arbitrary events and parameters that can be acted upon by the server or middle tier. The events can be partial page events or full page events.

Client action enabled components wrap client actions in a primaryClientAction element, as shown in the following UIX XML example:


...
<button text="Client action enabled button">
  <primaryClientAction>
    ...
    <!-- client actions here -->
    ...
  </primaryClientAction>
</button>
...    

Most UIX form components can use the primaryClientAction element to wrap client actions:

There are two basic client actions:

You can set the following attributes for firePartialAction and fireAction:

For form submitted events, you can also set arbitrary event parameters to send with the form in a partial page update event. Note that a formValue element must also be specified for each additional event parameter that you send.

Note: The Client Action is extended to allow rendering actions with a link instead of using JavaScript events. The getParameters method returns all the query parameters that are needed on the link. If the renderAsEvent method returns true, the renderer should render the script on one of the events (e.g. onClick, onChange etc.). If renderAsEvent returns false, the renderer has the option of rendering directly as a link.


About Partial Page Rendering
About LovOpenWindowAction Client Action

Editing the PrimaryClientAction Attribute
Working with Form Components

 

Copyright © 1997, 2004, Oracle. All rights reserved.