An action defines an act implemented when an event occurred and a relevant condition was examined. This action is meant for a firmly determined target, which concerns a single node or multiple nodes. To indicate the target, you need to formulate the XPath expression.
What needs to be defined for each action?
For each action, define:
- Main action (mainAction)
- Reverse action (inverseAction).
Optionally, you may define the reverse action. It is implemented only if the formulated condition has not been met and the condition permits that the reverse action may be implemented (useInverse = true).
Figure 9:
XUI schema - Action
Action | Description |
|---|---|
mainAction | Main action, executed with the positive examination of the condition. |
inverseAction | Reverse action (opposite), implemented with the negative examination of the condition.. |
...
Types of actions
There are three different types of actions:
...
| Codeblock | ||||
|---|---|---|---|---|
| ||||
<propertyChange>
<formulaExpression>"my change of model"</formulaExpression>
</propertyChange>
|
To set new model values, use a formula expression. With this expression, you can use complex XPath statements or extended functions. In the above example, the new value "my change of model" is set on the target node.
| Codeblock | ||||
|---|---|---|---|---|
| ||||
<uiAction methodName="setVisible"> <param name="visible" type="boolean" value="true"/> </uiAction> |
...
With an UI-action the method name and the parameters, which will be handed over, are required. In the above example the target element is hidden.