Custom Confirmation Messages

Custom confirmation messages are useful for displaying extra information that may help the user make a decision to proceed or go back. Bespoke messages can be added to confirmation screens using dynamic text components to display information, such as, names or totals. In addition, more than one confirm button may be required. These can perform similar functions, such as confirm only, or confirm and open another screen.

Creating simple confirmation screens is covered in the Actionflow Foundation Course. An extract from 1.13 Confirmation Message Configuration can be found below. A simple confirmation screen must be created before custom messages can be configured.

Configuring Custom Messages

Use dynamic text components on the confirmation screen to display messages containing attribute data, such as names, statuses and counts.

1. On your confirmation screen, add dynamic text and static text components, as required, to create your message
   1. 
   2. In this example, a number of static and dynamic text components have been used to create a message where the two company names can be dynamically mapped onto the screen and given different formats, e.g. bold, font size, etc.
   3. A similar result can be achieved using one dynamic text component if no formatting differences are required
      1. Image Added
2. Open the Actionflow containing the Confirmation

   Insert excerpt
   _action_phase _action_phase nopanel true

3. Within the Confirmation

   Insert excerpt
   _action_phase _action_phase nopanel true

   , map the attributes from the initiator screen onto the dynamic text components, e.g. company name
4. Create counts by configuring lookups to additional data, then using countElements within an Output Attribute on a 

   Insert excerpt
   _action_calculate _action_calculate nopanel true

    action
   1. See below worked example for full details on how to do this

Configuring Multiple Confirmation Buttons

Confirmation screens can contain multiple confirm buttons that perform similar functions, such as confirm only, or confirm and open another screen.

1. On your confirmation screen, additional buttons can be added and configured with an Action Method of Other and an Action Type of Confirmation on their 

   Insert excerpt
   _property_tabs _property_tabs name action nopanel true

2. On the Actionflow for the action, e.g. delete, ensure a Confirmation Phase is added before the Processing Phase, and that the Confirmation Phase contains an 

   Insert excerpt
   _action_screen _action_screen nopanel true

    action for the confirmation screen
3. Right-click on the 

   Insert excerpt
   _action_screen _action_screen nopanel true

    node and choose 

   Insert excerpt
   _mappings_configure _mappings_configure name button nopanel true

4. Create mappings for each confirmation button and click Confirm Mappings
5. Hover over the 

   Insert excerpt
   _action_screen _action_screen nopanel true

    node to see the additional output connections
   1. 

Worked Examples

Here's are worked examples using the Company Data (available from the Learning Centre).

In this example, we are using:  

• A Company Management screen containing a grid of the Companies data and a card container of their associated Employees - this screen was created using the Multi-Tile template
• A Company Merger Pop up screen containing:
  • two manual drop down fields of the company name's of the companies to be merged
  • two string fields showing the company ID's of the companies to be merged
  • a button to initiate the Actionflow - this screen was created using the Tile no Buttons template
• A Company Merger Confirmation screen containing a multiple static and dynamic text components, and buttons - this screen was created using the Confirmation template
• A Company Order Form screen containing form fields for the Orders data - this screen was created using the Edit Form template

Example 1: Custom Merger Message

In this example, a company acquisition screen requires a custom confirmation message to show the company names, and the quantities of employees and orders that will be affected by the merge.

Prerequisites

For this example, we'll add a custom confirmation message to a company merger Actionflow. If you have not completed 3.03 02 Bulk Update Action Configuration, expand the section below and follow the steps to create the company merger Actionflow.

Lookup Setup

1. Open the Company Merger Confirmation screen and familiarise yourself with the components available
2. Open the Actionflow on the Run Acquisition button on the Company Merger Pop up screen
3. Add a

   Insert excerpt
   _action_phase _action_phase nopanel true

    before the Processing Phase
   
   1. Name: Confirmation 
4. Select the CompanyMerger datasource as the Input 
5. Map into the Actionflow the four attributes from the screen:
   1. CompanyIDBeingAcquired
   2. CompanyIDDoingAcquiring
   3. CompanyNameBeingAcquired
   4. CompanyNameDoingAcquiring
6. Setup a 

   Insert excerpt
   _action_calculate _action_calculate nopanel true

    action that will be used to process the lookup data
7. Configure two lookups that will be used to retrieve the employees and orders for the company that is being acquired

Count and Open Screen Setup

1. Create two Output Attributes on the Calculate action that count the records being retrieved from the lookups
   
   

   Expand
   title How?
   Create an Output Attribute: Name: NumberEmployees Type: Integer Expression: countElements(emp) emp is the name of the lookup connector Create an Output Attribute: Name: NumberOrders Type: Integer Expression: countElements(ord)

   
   

2. Create an output connector from the Caqlcxulate Calculate action, then clikc click on the canvas to create an 

   Insert excerpt
   _action_screen _action_screen nopanel true

    action for the Company Merger Confirmation screenHover over the Company Merger Confirmation the Company Merger Confirmation screen

3. Map across the two attributes you just created on the Calculate action and the two Company Name attributes from the input on the confirmation screen

   Expand
   title How?
   Your Mappings setup should look similar to this: Image Added

   
   

4. Hover over the Company Merger Confirmation 

   Insert excerpt
   _action_screen _action_screen nopanel true

    action and click Confirm, then select anywhere on the canvas to connect to the Processing Phase

   Expand
   title Checkpoint

   
   

Testing

1. Return to the Company Merger Pop up screen
2. Select two companies from the drop downs and click Run Acquisition
3. The Company Merger Confirmation screen should appear with the details of the selected companies mapped to the screen
   1. Choose Cancel or Confirm

Example 2: Multiple Confirmation Buttons

In this example, we'll configure a confirmation screen for a save company action that has two confirmation buttons - one button will just confirm the save and one button will confirm the save and create a new order for the company. 

Lookup Setup

1. Open the Actionflow on the Save button on the Company Form
2. Rename the Processing Phase to Save Only Phase
3. Add a new phase after, Name: Save and Add Phase
4. Add a new phase before the Save Only phasePhase, Name: Confirmation
   1. 

Confirmation Phase Setup

1. On the Confirmation Phase, configure an input of On Click
2. Create an 

   Insert excerpt
   _action_screen _action_screen nopanel true

    action to open the Company Form Confirmation screen
3. Map on the input
4. Right-click on the 

   Insert excerpt
   _action_screen _action_screen nopanel true

    action and choose 

   Insert excerpt
   _mappings_configure _mappings_configure name button nopanel true

   Create an additional mapping for the ConfirmAndAdd button to see the mappings for both confirmation buttons

5. Hover over the 

   Insert excerpt
   _action_screen _action_screen nopanel true

    action to see the two output connections, then connect Confirm to the Save Only Phase, and ConfirmAndAdd to the Save And Add Phase
   

   Expand
   title Checkpoint

   
   

Save and Add Phase Setup

1. On the Save And Add Phase, configure an input of the CompanyForm datasource
2. Map the CompanyID and CompanyName attributes into the Actionflow
3. Set up a 

   Insert excerpt
   _action_save _action_save nopanel true

    action to save data to the Companies table, ensuring Auto Save Attributes is toggled on
4. Map Connect the input and map the CompanyID attribute to the Save action
5. Create an 

   Insert excerpt
   _action_screen _action_screen nopanel true

    action to open the Company Order Form screen
6. Map the Save action to the Open Screen action
7. On the Mappings between the Save and Open Screen actions:
   1. Map the CompanyName attribute from the input to the CompanyName attribute on the screen
   2. Map the CompanyID attribute from the table (not the input) to the Customer_ID attribute on the screen

      1. The CompanyID attribute is mapped from the table and not the input because for a new company an ID is not created until the record is saved to the table. If the CompanyID attribute was mapped from the input, it would be populated when saving an existing company but blank when creating a new company

         Expand
         title Checkpoint

         
         

Testing

1. Open the Company Management screen
2. Select either Add or Edit to open the Company Form
3. Enter/change details for a company and press Save
4. The confirmation screen will open, choose Yes + Create Order
5. This will save the company and open the Company Order Form populated with the company name and ID of the company just created/edited
   
   

Image Modified