JavaDDA Events in Unified Service Desk

Java data-driven adapter (JavaDDA) provides a set of events to trigger automation executions in the Hosted Application Toolkit (HAT). The events correspond to the events in the Java runtime. All events are bound to the controls on the user interface (UI). To register for the event, the control must be present in the UI. Use the FindControl activity to see if the control exists. This topic describes the JavaDDA events.

JavaDDA events

The following table lists the events available in the JavaDDA:

Event	Description
CheckBoxSelected	Invoked when the check box is selected (marker set).
CheckBoxCleared	Invoked when the check box is cleared (marker not set).
RadioButtonSelected	Invoked when the radio button is selected.
RadioButtonCleared	Invoked when the radio button is cleared.
ButtonPressed	Invoked when the button is pressed (versus a click, which is press-release).
ButtonReleased	Invoked when the button is released.
GotFocus	The event is raised when the control gets the focus.
LostFocus	The event is raised when the control loses the focus.
MenuSelected	Invoked when the menu item is selected.
MenuDeSelected	Invoked when the menu item is unselected.
MenuCanceled	Invoked when the menu selection is canceled.
TreeNodeCollapsed	Invoked when the tree node is collapsed.
TreeNodeExpanded	Invoked when the tree node is expanded.

Note

When multiple instances of the same external Java applications are hosted outside of the agent desktop, such as when the Java application is a session application, User Interface Integration (UII) can’t distinguish between instances unless the bindings have been authored in such a way that controls can be distinguished between the two instances. With typical Win32 applications, this is done by limiting to a particular process ID, but this isn’t possible with Java applications, and greater care must be taken in authoring the binding.

See also

JavaDDA
Use Data Driven Adapters (DDAs)