Chapter 5. GUI power tools: actions and triggers

Table of Contents

1. GUI actions and action implementations
1.1. Opening a GUI element: StandardGUIElementGUIAction
1.2. Running an EDW program: StandardProgramGUIAction
1.3. Visiting a URI: StandardURIGUIAction
1.4. Executing generic SQL statements: StandardExecSQLGUIAction
1.5. Emptying a table: StandardEmptyTableGUIAction
2. GUI triggers and trigger implementations
2.1. Purpose of GUI triggers
2.2. Types of GUI triggers
2.3. Trigger registration, linking and firing
2.4. Generating record IDs: StandardGenIdGUITrigger
2.5. Non-interactive lookups: StandardLookupGUITrigger
2.6. Generic SQL select statements: StandardSingletonSelectGUITrigger
2.7. Constant values as defaults: StandardConstantGUITrigger
2.8. Jack of all trades: StandardPascalScriptGUITrigger
2.8.1. The Environment object in script triggers
2.8.2. Other script trigger examples

We have seen the basic structure of an EDW GUI in the last chapter. As we have seen, the GUI is made up of elements, each of which represents a standard or custom form, or a launch point for an action (for example, an EDW program). You create custom forms when you need to link completely custom functionality to EDW's GUI catalog, but for simple search and data-entry needs the standard forms may be just enough. You augment the capabilities of standard forms by means of GUI actions a triggers. The following sections describe these objects in some detail, explains how to define them and documents the available types. The relevant section of the Advanced techniques chapter explains how to create entirely custom GUI actions and triggers.