ProcessActions - Action types

Enumarators overview

• OACT_command (1) - Command action
  
• OACT_expression (2) - Expression
  
• OACT_function (3) - Function action
  
• OACT_program (4) - Program action
  
• OACT_switch (5) - Switch action
  
• OACT_undefined (0) - Undefined action
  

Enumerator details

1. OACT_undefined - Undefined action
   

   Undefined actions are never executed. In order to disable an action temporarily, its action type might be set to undefined.

   Code: 0
   to list
2. OACT_command - Command action
   

   The command action is an action which call a shell command. In general, the ODE prefers to call programs via shell procedures, which provide more flexibility for describing the process.

   When calling shell commands, the console output is piped to the ODE and will be displayed in the output area after running the process. The process (foreground processing) or thread (background processing) waits,until the command is finished. In case of background processing the result is stored in the process queue and can be displayed when required.

   Parameters defined for the command call are passed to the procedure. The shell procedure has to be provided as an external file at the location as being defined in the call expression.

   When the procedure requires user input, the ODE will stop working, i.e. procedures called should never prompt the user (and should not contain pause commands).

   Sub actions are executed after running the command.

   Code: 1
   to list
3. OACT_expression - Expression
   

   Expression actions are bases on an expression. When a procedure has been defined for the action, the procedure should contain the expression to be executed.

   The action may also refer to a class expression, which must be an OSI expression implemented in the class of the object on which the action applies.

   Sub actions are executed after calling the expression.

   Code: 2
   to list
4. OACT_function - Function action
   

   Function actions are actions, which are defined in the type context of the object, on which the action applies. Since function actions have to be implemented in the context class, usually function actions refer to actions already defined in the ODE.

   Sub actions are executed after calling the function.

   Code: 3
   to list
5. OACT_program - Program action
   

   In contrast to a command, the program action refers to a single executable program. The program is called from the defined location with the parameters provided.

   The program is called in a separate process, i.e. the process does not wait until the process is being completed. When collection is switched on, the program is called for any instance in the collection.

   Since program actions potentially require user interaction, program actions are always started immediately and not sent to background or remote processing.

   Sub actions are executed after calling the program.

   Code: 4
   to list
6. OACT_switch - Switch action
   

   A switch action is an action which consists of a number of sub actions. The action corresponding to the resolved call expression will be executed when being defined in the list. Otherwise no action is performed.

   Subsequent actions might be of any action type, including switch actions, again. Usually, switch actions should not define parameters. When defining a parameter list, the resolved parameter list will be stored in the ACT_PARMS option variable, which might be referenced in sub actions.

   Code: 5
   to list