Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 17 Next »

What is a Delete Action?

The  Delete action deletes records for a selected table. 

Note: Delete actions will only delete records in tables with the Period of Transactional

Error rendering macro 'excerpt-include' : No link could be created for '1.09 Save Action Configuration'.

Creating Delete Actions

  1. Click the  Delete icon in the toolbar to display any existing tables in the application
    1. Existing tables can be dragged from the Repository onto the canvas, then choose  Delete to create a Delete node
  2. Alternatively, drag the  Delete icon from the toolbar onto the canvas
  3. In the Create Delete Action window:
    1. Enter a name
    2. Choose the Table from the drop down where the records will be deleted
    3. Select Create Action

When creating delete actions it can be useful to set up confirmation messages that allows users to confirm or cancel the deletion. See 1.13 Confirmation Message Configuration.

Worked Example

Here's a worked example using the School Data (available from the Learning Centre).

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 Application.

In this example, we want to be able to delete courses in the School Courses grid on the Course Management screen. We will also configure the Delete Actions on the input form

Note: When creating new screens and input forms in PhixFlow, Grid Actions and Form Actions wizards are available to configure the Delete actions for you. For the purposes of understanding the mechanics of Actionflows, we will create these manually.

Delete Action on Grid

  1. On the Course Management screen, right-click on the  button and choose  Add Actionflow
  2. Enter a name for the Actionflow,
    1. Name: Delete Course (Course Grid)
    2. Select Confirm
  3. Select Click to Connect and for the input, choose the School Courses  Grid datasource, then select Connect Input
  4. In the Mappings window that opens, drag the CourseID attribute from the left (School Courses Grid) to the right (Input Connection Point)
    1. Select Save
  5. Click and drag the  Delete icon from the toolbar onto the canvas
  6. In the Create Delete Action window enter:
    1. Name: DeleteCourse
    2. Table: choose School Courses
    3. Select Create Action
  7. Click and drag the  icon onto the  Delete action node
  8. Right-click on the in connector and choose  Open Mappings
    1. Drag the CourseID attribute on the left onto the CourseID attribute on the right
    2. Select Save
  9. Close the Actionflow to return to the Course Management screen
  10.  Lock the screen and select a record in the grid, then press the  button

Delete Action on Form

  1. On the Course Management screen, select the  or  button to open the Course Form
  2. Right-click on the  button on the Course Form and choose  Add Actionflow
  3. Enter a name for the Actionflow,
    1. Name: Delete Course (Course Form)
  4. Repeat the above steps to configure the Actionflow but make the following changes:
    1. the input is the Course  Form
    2. in the Settings, toggle on  Close screen after action completes - this will close the Course Form when  is pressed
  5. Once you have configured the Actionflow, return to the Course Management screen
  6.  Lock the screen, select a record in the grid and press the   button
  7. On the Course Form, press the  button
    1. If the Actionflow has been set up correctly, the Course Form will close and the selected record will be 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. 


1.13 Confirmation Message Configuration

  • No labels