Show alert
Actions – Abstract
The action Show alert creates a specific Type of note that displays the text information displayed by the Alert title and Alert message parameters to the user.
The action Show alert creates a specific Type of note that displays the text information displayed by the Alert title and Alert message parameters to the user.
Optionally, a Target element can be linked, which is to receive the focus in connection with the alert. If the Target element allows this, based on its type and the settings valid at runtime, the following happens:
In connection with the Type 'Alert box' (default), the focus is only set on the Target element when the hint displayed as a dialog box is closed again.
For all other Types, which are displayed as so-called 'notifications' at the right edge of the screen, the focus is set immediately when the message appears.
The text information for the Alert title and Alert message parameters can be assigned using two different methods:
|
Method for providing text information Assigning a localization entry |
Alerts |
||||||||||
|
|
Whenever a reference to a localization entry is created or updated, it applies to each supported Locale. However, the assignment can be subsequently overridden for selected languages by making a direct entry (see below). At runtime, the reference is interpreted according to the Locale used in the session via Localization or Company specific localization. In the example, the German text 'Hinweistitel' appears as the alert title, whereas in English 'Alert title' would appear. |
||||||||||
|
Direct input (text, label printout or a combination of both). Examples (with different Types):
|
Direct input must always be entered individually for each supported Locale, otherwise no text may appear in the respective language. As shown in the last example, Calculation expression can also contain references to localization entries. |
The Type parameter defines the appearance of the alert at runtime and also has functional effects:
|
Type |
Category |
Example |
|
Alert box |
Dialog
|
|
|
Notification: Info |
Notification
|
|
|
Notification: Error |
|
|
|
Notification: Warning |
|
|
|
Notification: Success |
|
Example
A form lists a table of order positions in a Repeatable element container.
At the push of a button, the most expensive individual item is determined, the associated amount is displayed and the text of the corresponding position is then focused.
Runtime example:
Under Goto ... the Maximum Button was pressed. The most expensive order position is determined and the amount appears in an 'alert box':
After confirming the reference with OK, the focus is set in the 'Order position' Text field of the corresponding purchase order:
Confiiguration:
|
|
For the Price Text field, which allows the input of numerical values, the behaviour 'maximumAlert' shown on the left is configured:
Under the Actions on 'true' a Show alert action is executed, which uses the Calculation expression already used in the behaviour type to determine the maximum value searched for, in addition to the Alert title 'MAXIMUM' in the Alert message. The type selected is 'Alert note', since the linked Target element, the 'Order position' Text field, should only be focused after the note has been acknowledged. |
|
|
In order to trigger the evaluation of the 'Order position' via the Maximum Button, the 'gotoMax' behaviour shown on the left is configured
►NOTE◄ If the maximum value for the amount is found in more than one invoice item, a separate note is generated for each discovery, which must be acknowledged. As the alert boxes appear 'stacked', the focus moves backwards through the list, as the last displayed alert is confirmed first. |
►NOTE◄ The described configuration can be optimized in terms of performance, so that the calculation expression $max($el(48,true))has to be executed only once. If this expression is used as a Value expression instead of $input in the Execute behaviour action of the 'gotoMax' behaviour, the called behaviour 'maximumAlert' gets the maximum value as $input, to which the Compare with behaviour type as a Calculation expression and the Show alert action can refer as an Alert message. However, the configuration then appears somewhat less transparent. Therefore the procedure above is different.