User confirmation

Prev Next

See also: User prompt

The Behavior type User confirmation determines the Boolean value for the selection of the actions to be performed by interactive decision.

images/download/attachments/177913747/image-2024-9-25_11-46-34-version-1-modificationdate-1727257593782-api-v2.png

The Behavior type User confirmation determines the Boolean value for the selection of the actions to be performed by interactive decision.

A simple modal selection dialog is displayed to the user with the buttons Yes and No:

  • Actions on "true" are only executed if the user confirms the dialog by clicking Yes.

  • Actions on "false" are executed when the user selects No or closes the dialog by pressing 'X' (top right).

In both cases any input data ($input) is passed on to the actions.

Configuration

  • The text input for the Title appears in the title bar of the dialog.

  • The text input for the Message should inform users about the meaning or effects of selecting Yes or No.

â–ºNOTEâ—„ Given behavior data (provided by Events (Form designer) or when the behavior is called by action Execute behaviour) can be referenced e.g. via $input in the text.

Use case example

A portal provides a Button which closes it by the action Request close. Since a careless click on this Button could result in the loss of any data entered, a prompt will offer the possibility to cancel the 'Close' action.

Only if the user confirms with Yes, will the portal actually be closed.

Configuration

images/download/attachments/177913747/image-2024-9-25_12-19-6-version-1-modificationdate-1727259546158-api-v2.png

  • A behavior is configured for the Button that reacts to the Triggering event Click.


  • Meaningful text for the parameters Title and Message is entered for the Behavior type.


  • Under Actions on "true" the Request close action is selected.

Runtime example

images/download/attachments/177913747/image-2024-9-25_12-20-12-version-1-modificationdate-1727259611807-api-v2.png