Relationship: Application Options have Application Actions

Using the Application Options have Application Actions relationship, an AWM application can be assigned actions which are executed on the application level. Action descriptors referenced using this relationship appear either in the context menu of the application entry or are executed automatically on specific conditions. Actions can be hidden or deactivated on certain conditions. An action Visible or Enabled condition determines when an action should be visible and activated. See Enabled/Visible Condition for more information.

Attribute	Type	Description
TargetID *	ActionDescriptor	The reference to the action descriptor.
ActionVisibleCondition	ActionVisibleCondition	This complex attribute lets you define rules for when the action should be visible in the context menu of the application.
ActionEnabledCondition	ActionEnabledCondition	This complex attribute lets you define rules for when the action is activated. Non-activated actions are disabled, and cannot be executed by the user.
Default_Action [U]	Boolean	Defines whether this action should be carried out by a double-click on the application entry. Only one application action can be declared as the Default_Action. The default value is false.
Label [O]	String	Labeling of the action in the context menu. If no label is stated, the label of the referenced action descriptor is used.
Separator_After	Boolean	Determines whether to insert a separation line behind the context menu entry. The default value is false.
Execution Type *	Selection	Determines when to execute the action. Valid values are: Manual The action appears in the context menu of the application entry. OnLoad The action is executed when the AWM model is loaded. This can be when the application is loaded manually or automatically when starting Eclipse. OnFirstLoad The action is executed when the AWM model is loaded but only once during an Eclipse session. OnUnload The action is executed when the AWM model is unloaded. This can be when another application is loaded manually or automatically when closing Eclipse. Note: Manual is the default value.
Skip model update check	Boolean	Determines whether a model update check should be executed when the action is executed. This is only relevant for actions which are executed when loading the model.

Example

Application actions of execution type Manual can be actions to create a new object. Another sample can be an action to display and change application specific options.

Application actions of execution type OnLoad or OnFirstLoad can be actions to initialize the connection to a remote application system, for example, a remote database system. In this case, the execution type depends on the point in time when the connection is shut down (with the unload of the application loading another application or only when closing the Eclipse session).

Application actions of execution type OnUnload could be actions to shutdown the connection to a remote application system, for example, a remote database system.