Form data loaded

The form data was loaded or reloaded, for example, because a business object was selected in an overview or after ‘New’ or ‘Save’.

• If the action Invalidate context is followed by displaying the same form with a changed context, this change type does NOT apply.

• If the action Invalidate context is followed by the display of another form with the changed context, this change type is already effective in this form.

• The form data is also reloaded if an Event handling is executed from the form using the action Eigenes Aktionsevent auslösen which changes data.

Exclusively by the user(default value)

The user has changed the value of the element manually and directly.

►NOTE◄ When editing text interactively, every single keystroke that changes the content triggers the ‘Changed’ event. If a string ‘ABC’ is typed character by character into an empty text field, the behaviour is addressed three times with the values ‘A’, ‘AB’ and ‘ABC’. Depending on the behaviour, the actions (on true or false) are called several times. This should be taken into account when designing behaviour and actions. If, for example, the ‘User confirmation’ behaviour is to be used to respond to a text input, it is not helpful if the corresponding dialog appears after each keystroke. If necessary, the characteristic for the trigger ‘Changed’ can be adjusted by the 'Execute later once (ms)’ parameter so that the user can enter several characters or make other modifications to the content of the element before the data is passed to the behaviour (Debounce).

Other events (such as Focus out or Key pressed may also be better suited to respond to text entries. Both examples require a certain degree of cooperation on the part of the user, who must then leave the field or press the ‘Enter’ key to formally complete the input.

Element data changed

The element data has changed depending on the data field or through an action 'Populate element data'. The term ‘element data’ refers to the data content that was actually transferred to the form data for an element.

The Value of an element may differ from this element data if the element was changed interactively (see previous change type) or by program logic (see the following change type) and has not been validated since. The validation of all elements takes place when saving at the latest, but can also be triggered specifically for a certain element by Behaviours in the form (Validate element or Validate element and call profile).

Value set by program

The Value of the element was changed by a program logic e.g. by the action 'Set value' or by a Berechnung.