Confirmation Actions

Confirmation Actions (Action Type 3) display a Yes/No dialog box that allows users to make decisions at critical points in business processes. Unlike Message and Error actions that simply inform users, Confirmation actions implement branching logic where different actions execute based on whether users select Yes or No. This section explains when Confirmation actions are appropriate, how to configure branching logic, and best practices for creating effective decision points.

9.1 When to Use Confirmation Actions

Confirmation Actions serve as decision gates in business processes, allowing users to choose whether to proceed with an operation or take an alternative action. They are most appropriate when policies require user judgment rather than automatic enforcement.

Appropriate Use Cases:

• Override Decisions: Allow authorized users to override soft limits or advisory policies

• Approval Shortcuts: Confirm that users have obtained required approvals before proceeding

• Risk Acknowledgment: Require users to acknowledge risks or special circumstances

• Alternative Action Selection: Allow users to choose between different processing paths

Example Scenarios: Discounts above standard limits (confirm manager approval received), orders to customers with past-due invoices (confirm payment arrangements made), changes to critical master data (confirm changes are intentional), expedited processing requests (confirm additional costs are approved).

9.2 Configuring Confirmation Actions

Confirmation actions have unique configuration requirements because they support branching logic (different actions for Yes vs. No responses).

Configuration Steps:

1. Create the validation condition that determines when the confirmation dialog should appear

2. Add a new action and set Action Type = Confirmation

3. Configure the confirmation question text that users will see

4. Define "On Yes" actions that execute if users select Yes

5. Define "On No" actions that execute if users select No

The branching capability makes Confirmation actions more complex than Message or Error actions, but provides powerful workflow control.

9.3 Understanding Branching Logic (Yes/No Actions)

When a Confirmation action executes, users see a dialog box with the question text and two buttons: Yes and No. Based on their selection, one of two action sequences executes.

On Yes Actions: If the user selects Yes, all actions defined in the "On Yes" section execute in sequence. Common Yes actions include allowing the transaction to proceed normally (no further action), sending email notifications, logging approval confirmations, or assigning field values.

On No Actions: If the user selects No, all actions defined in the "On No" section execute in sequence. Common No actions include displaying an Error action to block the transaction, showing a Message with alternative instructions, or opening a URL to approval request forms.

Example Branching Logic:

9.4 Approval Workflow Examples

Example: Discount Approval Confirmation

Business Requirement: Discounts above 15% require manager approval. Prompt users to confirm they have approval.

Configuration:

• Trigger Table: 37 (Sales Line)

• Condition: [37:27] is >15

• Confirmation Text: "You are applying a discount of [37:27]%, which exceeds the standard limit of 15%. Have you obtained manager approval for this discount?"

• On Yes Actions: Message "Please document the manager's name and approval date in the order notes."

• On No Actions: Error "Please obtain manager approval before applying discounts above 15%. Contact your department manager for approval."

9.5 Best Practices for Confirmation Dialogs

Write Clear Questions: Make the question specific and easy to answer with Yes or No. Avoid complex questions that require paragraph explanations.

Provide Context: Include relevant values or circumstances in the question so users can make informed decisions.

Make Consequences Clear: Users should understand what happens if they select Yes vs. No before making their choice.

Avoid Confirmation Fatigue: Do not overuse confirmations. Too many interrupting dialogs train users to click Yes automatically without reading