An event defines the kind of trigger and the relevant range (scope) for the processing of the condition, and respectively all actions. A rule is processed in these circumstances:
- The occurrence of a change corresponds to the defined kind of event
- The occurrence of a change affects the defined scope.
Figure 79: XUI component - Event
Fieldname |
Default |
Description |
|
Type |
change |
Defines the type of event. See section 2.5.1.1. |
|
Execution mode |
clientAndServer |
Defines if this rule should be executed on client only, server only or both. |
|
Does concern none-serializable source If this setting is deactivated, as soon as the underlying node is no more serialized the rule stops being executed. In this case, a previously indicated validating message is removed, regardless of its category (incomplete, hint, info, error). |
Yes |
Defines whether the rule is to be executed, if the underlying node is no longer serializable. |
|
Scope |
sourceAndReferencedNodes |
With the specification of its own Java class, the condition itself can be implemented. The class must implement the condition interface. If a formula expression and its own class are indicated, both conditions must be fulfilled, in order that the actions be executed. |
|
For example, to inform yourself about the entry of a list element or the selection from a choice (modeled Choice), you must select the following type and scope for the list element: Type=„structureChange (addNode)" and Scope=„sourceOnly".