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.
XUI component - Event
Fieldname | Default | Description |
|
|---|---|---|---|
Type (deprecated!) | change | Defines the type of event. See section Event. |
|
| Event trigger | commit copyContent domInitialized domReady onCreation aboutGoNext (go to next page) goNext (go to next page) aboutGoPrevious (go to next page within pagelayout) goPrevious (go to next page within pagelayout) listItemSelected pasteContent aboutToPersist persistent propertyChange aboutToSerialize serialized structureChange (add) structureChange (remove) aboutToValidate validated visualized nodeVisited (html only) | ||
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 (deprecated!) | 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. |
|
| Scopes | source referencedNodes allDescendants directDescendants all directParent parent siblings |