Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
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.
borderColor | grey |
---|---|
borderWidth | 2 |
borderStyle | dashed |
The below text is taken from 1.13 Confirmation Message Configuration.
Configuring Custom Messages
- 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
- See below worked example for full details on how to do this
Configuring Multiple Confirmation Buttons
On your confirmation screen, additional buttons can be added and configured with an Action Method of Other and an Action Type of Confirmation on theirWhat are Exclusion Groups?
Exclusion Groups are a way to group Actionflows that should not be running at the same time.
Where multiple Actionflows have the same exclusion group, only one Actionflow will be able to run at any one time. Attempting to run a second Actionflow with the same exclusion group will return a warning message and the Actionflow will not run. This applies whether the Actionflow is run manually or automatically using a schedule.
Exclusion groups are evaluated before any Actionflows are started. When an Actionflow with an exclusion group is triggered, if no other Actionflow with the same exclusion group is already running then the Actionflow will continue. The action will be considered to be using this exclusion group from this point until the Actionflow has completed.
Setting Exclusion Groups
- Open an Actionflow and open its
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 anInsert excerpt _property_tabssettings _property_tabs name actionsettings nopanel true Insert excerpt _action_screen _action_screen action for the confirmation screenRight-click on thenopanel true Insert excerpt _action_screen _action_screen node and choosenopanel true Insert excerpt _mappings_configure _mappings_configure name button nopanel true - Create mappings for each confirmation button and click Confirm Mappings
- Hover over the
Insert excerpt _action_screen _action_screen node to see the additional output connectionsUnder Basic Settings, populate the Exclusion Group field with any text to indicate the groupnopanel true - This field is case insensitive and can take any free text
- Repeat this with other Actionflows to add them to the same Exclusion Group
Worked Example
Here's a worked example 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 A Company Orders screen containing two grids of the Orders and OrderLines data - this screen was created using the Edit Form Multi-tile template
Tip |
---|
If you are completing this chapter as part of the Actionflow course and using a training instance, the data and screens have already been pre-loaded into the Actionflow Advanced Application. For this example, we'll be working on the Company Merger ConfirmationOrders screen. |
Prerequisites
ForExample: Setting an Exclusion Group
In this example, we'll add a custom confirmation message to a company merger Actionflow. If you have not completed 3.03 Bulk Update Action Configuration, expand the section below and follow the steps to create the company merger Actionflow.
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.
Lookup Setup
Open the Company Merger Confirmation screen and familiarise yourself with the components availabletwo Actionflows to the same exclusion group to see the warning that appears when triggering both Actionflows at the same time. This example is just for demonstration purposes.
Actionflow Setup
Hover over the- Open the Company Orders screen
- Open the Actionflow on the Run Acquisition Edit button on the Company Merger Pop up screenAdd a and open the
before the Processing PhaseInsert excerpt _actionproperty_phasesettings _actionproperty_phasesettings nopanel true - Name:
Confirmation
- Name:
- Select the CompanyMerger datasource as the Input
- Map into the Actionflow the four attributes from the screen:
- CompanyIDBeingAcquired
- CompanyIDDoingAcquiring
- CompanyNameBeingAcquired
- CompanyNameDoingAcquiring
Setup a - Configure lookups to retrieve the Employees and Orders for the company that is being acquired
title | How to Configure the Employees Lookup |
---|
- Under Basic Settings, populate the Exclusion Group field with any text, e.g.
Orders
- Repeat these steps with the Actionflow on the Add button on the Company Orders screen
- On the Actionflow on the Add button, create a
actionInsert excerpt _action_calculate _action_calculate nopanel true
Give the lookup a suitable name
Click onto the canvas, then enter a suitable name for theSelect an Output Attribute of EmployeeID, then select Next
For the Incoming Mappings, choose CompanyIDBeingAcquired, then select Next
For the Outgoing Mappings, map across EmployeeID to the Calculate action, then select Confirm and create filter
For the filter, match the CompanyID in the data to the Incoming Mapping
Expand | ||
---|---|---|
| ||
title | How to Configure the Orders Lookup |
---|
- with
Select an Output Attribute of Order_ID
For the Outgoing Mappings, map across Order_ID to the Calculate action
For the filter, match the Customer_ID in the data to the Incoming Mapping
Expand | ||
---|---|---|
| ||
Count and Open Screen Setup
- Create two Output Attributes on the Calculate action that count the records being retrieved from the lookups
Expand Create an Output Attribute:title How? - Name:
-
Delay
- Type:
Integer
- Expression:
-
sleep(
- emp is the name of the lookup connector
- Create an Output Attribute:
- Name: NumberOrders
- Type: Integer
- Expression: countElements(ord)
Create an output connector from the Caqlcxulate action, then clikc on the canvas to create an
Expand | ||
---|---|---|
| ||
Testing
- Return to the Company Merger Pop up screen
- Select two companies from the drop downs and click Run Acquisition
- The Company Merger Confirmation screen should appear with the details of the selected companies mapped to the screen
- 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
- Open the Actionflow on the Save button on the Company Form
- Rename the Processing Phase to Save Only Phase
- Add a new phase after, Name: Save and Add Phase
- Add a new phase before the Save Only phase, Name: Confirmation
Confirmation Phase Setup
Expand | ||
---|---|---|
| ||
Save and Add Phase Setup
- On the Save And Add Phase, configure an input of the CompanyForm datasource
- Map the CompanyID and CompanyName attributes into the Actionflow Set up a
- Map the CompanyID attribute to the Save action
- Create an
20)
- This will add a delay into the Actionflow for demonstration purposes. See sleep
- Insert the Delay Calculate action onto the connector between the
andInsert excerpt _input _input nopanel true
action to open the Company Order Form screenOn the Mappings between the Save and Open Screen actions:Insert excerpt _action_screen _action_screen nopanel true - Map the CompanyName attribute from the input to the CompanyName attribute on the screen Map the CompanyID attribute from the table (not the input) to the Customer_ID attribute on the screen
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
title | Checkpoint |
---|
Testing
- Open the Company Management Company Orders screen
- Select either Press Add or Edit to open the Company Form
- Enter/change details for a company and press Save
- The confirmation screen will open, choose Yes + Create Order
- This will save the company and open the Company Order Form populated with the company name and ID of the company just created/editedthen Edit
- The warning message will appear
- After 20 seconds, the Order Form will open