ADM_Action - Action specification
The ODE supports different types of actions, which might be configured by the developer. Actions supported are described in ADM_Action.
Each action consists of a command and a list of parameters. The command as well as parameters may contain any number of option variables or values from the given context. Option variables might have been set also in the environment or configuration file passed when calling the object development environment.
Action command and parameters might be constructed from different option or expression variables.
Actions defined in the environment are processed by ProcessAction with the action name passed from the action caller. When defining a GUI action, the action name has to correspond to the environment action name, while the function action called is ExecuteEnvAction.
Before executing the action it will be sent to the process queue. Thus all actions may run locally in the fore- or background or on a remote processor machine.
When an action, which is not a switch action, has got a sub action list, sub actions are executed after executing the calling expression of the action. When the calling expression is empty, only sub actions are called.
The following call expression
${ if ( %DEBUG% == YES ) 'd'; else '';}$Proc
returns dProc in case DEBUG is set to YES and Proc otherwise.
- object_variable - Object variable
- object_path - Object path
- collection - Process collection
- call_expression - Call expression
- parameters - Parameters
- start_message - Start message to be displayed when running the action
- stop_message - Stop message to be displayed when terminating the action
- environment - Environments referring to the action
- action_list - Action list
- parents - Parent for composite action
- procedures - Procedures defined for the action
- response_files - Response files references in action procedures
- ik_name - Primary key