Open Confirm

Overview

The Open Confirm action displays a confirmation dialog, a modal window that overlays the page and requires user interaction. This dialog presents critical information and blocks interaction with the rest of the page until the user takes a specific action (e.g., clicking a confirmation button).

When to Use Confirm Dialogs

Use Confirm dialogs when you need explicit user acknowledgement of important information or decisions. They are intentionally disruptive to ensure the user doesn't miss the message.

Typical Use Cases

• Confirming irreversible actions, such as deleting data.

• Communicating critical system messages, like scheduled maintenance downtime.

Difference from Alert Modals

While visually similar to Alert Modals, Confirm dialogs require users to interact with them before continuing. The user cannot simply ignore or dismiss the dialog without taking action. The page content behind the dialog is inaccessible until the Confirm dialog is closed.

Configuration

Property	Description	Possible Value
Label	The text displayed in the confirmation dialog's header.	Any text string.
Message	The main content message displayed in the confirmation dialog.	Any text string.
Variant	Determines the appearance of the confirmation dialog. Controls whether a header is displayed.	With Header, Without Header (or similar, depending on your implementation).
Theme	Sets the color theme for the header (if a header is displayed).	Default, Shade, Inverse, Alt Inverse, Success, Info, Warning, Error, Offline (or your specific theme options).
On Confirm	Allows you to define a subsequent interaction that triggers when the user clicks the confirmation button (e.g., "OK").	This likely refers to configuring another interaction (e.g., Navigate, Save Record, etc.). This is not a simple text value.

Configuring the "On Confirm" Action

The "On Confirm" setting lets you choose what happens after the user clicks the confirmation button (usually labeled "OK") in the Confirm dialog. You can link this button click to another interaction, creating a sequence of actions.

Available Actions:

You can trigger these actions when the user confirms:

• Show Toast: Display a brief, temporary message to the user (e.g., "Record saved successfully!").

• Open Flow Dialog: Launch a new Flow within a dialog window.

• Open Dynamic Component Dialog: Display a dynamically configured component inside a dialog window.

Example: use the On Confirm interaction before deleting a record

In this example, we demonstrate how to use the "On Confirm interaction" to prompt end-users for confirmation before deleting a record.

Practical use cases

Some practical use cases for the Open Confirm interaction with next actions after clicking "OK" include:

1. Deleting a record: Display a confirmation message, ensuring users know the consequences before proceeding with the deletion. Upon clicking "OK," the record is removed, and a follow-up interaction or notification confirms the action's success.

2. Submitting a form: When users submit a form, an Open Confirm action can be triggered, providing them with a final review opportunity. After clicking "OK," the form is submitted, and a success message or redirect can be initiated.

3. Confirming a high-priority action: For actions with significant impact, such as changing user permissions or approving a substantial financial transaction, the Open Confirm interaction ensures users are fully aware of the implications. Clicking "OK" executes the action and can be followed by an audit log entry or a confirmation email to relevant stakeholders.