Actions

Actions are executions of rule sequences with predefined parameters or they call up specific screens.

Figure 45 Action Configuration

Creating a new Action

In order to create a new action, select new in the action inventory and add the desired properties of the action.

Field Contents
Code Code of the action. This code has to be unique and is used to identify actions when adding them to inventories or menus. For this reason, please refrain from using cryptic codes and make them as transparent as possible.
Description Description of the action, this should be preferably a human-read- able description to help administrators in determining the purpose of the action.
Parameters The parameter to execute, this is a ;-separated list.
Confirm Presents a dialog box for confirmation before execution
Input type This determines the input type to which the action is applied. This can be none, single ID, multiple ID, single value object, multiple value object, file or communication.
Rule The rule sequence to call.
Event Used for client side events (for example select all, which has no communication to the server)
Output type The type of output which can be undefined, none, screen (opens a screen) or file (results in a save as dialog box)
Screen Used to open a specific XGL screen
Input screen When you want to pass additional parameters to your action, you can use the input screen to capture them
Note type You can specify which note you want to show up on an action by selecting a note type on it.
Edit This should be deselected to create a read-only variant of the screen.
Refresh Select this to refresh the contents of the list view. Note that this has an impact on performance.

Table 43 Entity Configuration

Changing the Translations for an Action

On the translations tab of the action, translations for the four available languages can be entered. Note that this can be done in the system-wide translations inventory as well. The inventory presented here is simply a convenient alternative.