Delete Action Configuration
What is a Delete Action?
The
Note: Delete actions will only delete records in tables with the Period of Transactional.
For the full list of Delete action
Creating Delete Actions
Click the
icon in the toolbar to display any existing tables in the applicationExisting tables can be dragged from the Repository onto the canvas, then choose
to create a Delete node
Alternatively, drag the
icon from the toolbar onto the canvasIn the Create Delete Action window:
Enter a name
Choose the Table from the drop down where the records will be deleted
Select Create Action
Creating Delete Actions for File Tables
These settings are in addition to the steps above.
Confirmation Messages
When creating delete actions it can be useful to set up confirmation messages that allow users to confirm or cancel the deletion. See Confirmation Message Configuration and Custom Confirmation Message Configuration.
Worked Examples
Here's a worked example using the School Data (available from the Learning Centre).
In this example, we are using:
A Course Management screen containing a grid of the School Courses data - this screen was created using the Tile with Buttons template
A Course Form screen containing form fields and associated with School Courses data by a background filter - this screen was created using the Edit Form template
If you are completing this chapter as part of the Actionflow course and using a training instance, this data has already been pre-loaded into the Actionflow Foundation Application. For this example, we'll be working on configuring buttons on the Course Management screen and Course Form screen.
We want to be able to delete courses on a Course Management screen, using the delete button on the Course Management screen and on the Course Form screen. To do this, we will creating two Delete Actionflows. Both will delete the selected record.
Example 1: Delete Action for Grid
Create a Delete Action to delete courses in the School Courses grid on the Course Management screen.
On the Course Management screen, right-click on the
button and choose
Enter a name for the Actionflow,
Name:
Delete Course (Course Grid)Select Confirm
Select Click to Connect under Connections and for the input, choose the School Courses
View Component, then select Connect InputIn the Mappings window that opens, notice that by default the data being used is the selected record
Drag the CourseID attribute from the left (School Courses Grid) into the Drag and Drop area on the right (Input Connection Point)
Select Save
Click and drag the
icon from the toolbar onto the canvasIn the Create Delete Action window enter:
Name:
DeleteCourseTable: choose School Courses
Select Create Action
Click and drag the
icon onto theaction node on the canvasRight-click on the in connector and choose
Select Map by Name to map the CourseID attribute on the left onto the CourseID attribute on the right
Select Save
Checkpoint
Close the Actionflow to return to the Course Management screen
- the screen and select a record in the grid, then press the
button
Example 2: Delete Action for Form
Create a Delete Action to delete courses in the School Courses grid on the Course Form screen.
On the Course Management screen, select the
or
button to open the Course Form
- the screen
Right-click on the
button on the Course Form and choose
Enter a name for the Actionflow,
Name:
Delete Course (Course Form)Click Confirm
Repeat the above steps to configure the Actionflow but make the following changes:
the input is the Course
in the Settings, toggle on
Close screen after action completes - this will close the Course Form when is pressed
Checkpoint
Once you have configured the Actionflow, return to the Course Management screen
- the screen, select a record in the grid and press the
button
On the Course Form, press the
button
We can see that the Actionflow is working correctly because the Course Form closes and the selected record is deleted from the School Courses grid
Why do we not reuse the Delete Course Actionflow?
An Actionflow can be reused where the same Actionflow setup is required but with a different input data. The setup of the two Actionflows we created above have one key difference - the Delete Course (Course Form) Actionflow has Close screen after action completes enabled.
If we were to reuse this Actionflow with two different inputs (grid and form), the Close screen after action completes option would need to be consistent across both instances of the Actionflow.