Actions are defined using the Actions table on the Perspective tab. Each action identifies the trigger conditions by defining the combination of <content,view,event> that it responds to. An empty value means that it matches all possible events. For example <CubeData,select> matches the select event on CubeData (the content) in any view. For event name matching, only the text string up to the first colon is matched. This allows <MyChart,MyView,click:SomeURL> to be matched by an action defining <MyView,click> - which means any click on MyView.

Only actions which are marked as enabled are eligible to be invoked in response to an event. This allows a subset of actions and events to be tested and verified without side-effects from others.

Multiple actions can be triggered by a single event, if they all match the event attributes. The order of invocation is based on the order of actions in the Actions table. Actions can be raised or lowered in the action list to control the order of execution.