Three components make up an action:
On |
Specifies which event should trigger an action, such as a keystroke or a mouse click. |
Action |
Specifies what should happen when the On trigger occurs, such as display a message, launch a program, or cancel a test. |
Target |
Specifies a target used by the action. Targets can be chapters, sections, pages, tests, surveys, questions, objects, or variables. The Action defines which targets can be used. |
These three parts work together to create the end result. Depending on where you are adding an action, the options available to you will vary.
Actions added to organizational levels including the project, chapters, sections, pages, tests, test sections and surveys adhere to the same inheritance principles as other objects within project. That is, if an action is added to the project level, the action will execute on every page of the project if the action is triggered. Similarly, if an action is added to a chapter, section, test, survey or test section, it will execute on every page within the chapter, section, test, survey, or test section, respectively, if the action is triggered. Finally, if an action is added to a page, it will only execute on that page if the action is triggered.
You can add one or many actions to an object. For example, a button might contain several actions: Hide Image_1, Hide Text Block_1, Stop Audio_1, Show Image_2, Show Text Block_2, Play Audio_2. The order of the actions is important. For example, an action of Exit/Close project before an action of Modify Variable may cause issues since the project is closing before updating the variable. Additionally, you can create groups of actions. Action groups are useful when you want to run a set of actions as a single command. For details, see Grouping actions.
The following table lists all events, actions, and targets available in project:
On |
Action |
Target |
Any Key |
Cancel Test/Survey |
Chapter, Section, or Page |
See also:Understanding inheritance
© Copyright ELB Learning 2025