Choose the Best Data Action Class to Extend
Before you start writing your custom data action extension, decide which of the existing data action classes you want to extend. Choose the data action class that provides functionality that most closely matches what you want your data action to do.
Each data action inherits from the AbstractDataAction class
as shown in the class diagram. The class diagram shows the two abstract data action
classes (AbstractDataAction and
AbstractHTTPDataAction) and the four concrete data action classes
(CanvasDataAction, URLNavigationDataAction,
HTTPAPIDataAction, and EventDataAction) that you
can extend. Each data action that you provide must extend one of these classes. Which
class you extend depends on the behavior you want to implement when you invoke your data
action. Most third-party data actions are likely to extend either
URLNavigationDataAction, HTTPAPIDataAction or
EventDataAction.
Regardless of which class you extend, when your data action is invoked, you're provided with metadata describing the full context of the data-point from which the data action is invoked. See Data Action Context.