This page provides details of the properties for the delete node.

Overview

Use a

A delete node will only delete records from a table with a Type of Transactional.

The Delete node will persist Audit History of records when they are deleted. This is achieved by superseding the previous record and adding a new deleted record into the next recordset. This persists the history of the record. If you wish to purge records from your PhixFlow system entirely including Audit History see Bulk Delete Node Properties

Example

In the Actionflow instance illustrated in the screenshot above, an application has a list of Companies in a grid. When the user clicks the delete button, the Actionflow runs.

1. The Primary Key of the selected records on the All Companies grid are mapped onto the Input Connection Point.
2. The Delete Node uses the mapped Primary Key to select the records from the All Companies table and delete them.

Insert excerpt
_property_tabs _property_tabs name basic-h nopanel true

Basic Settings

Mapped Attributes

File Tidy Up Settings

Excerpt
name FileTidyUp
Where the selected table is a Insert excerpt _tableFile _tableFile nopanel true , the delete action can handle the associated file differently to the records, if required, e.g. delete the records but not the file. Note: The deletion/moving of the file occurs before the records are deleted. Field Description When Records are Deleted... Choose from: Leave the associated file in the uploaded directory: leave the file on the server Delete the associated file: delete the file from the server Archive the associated file to specified directory: archive the file to a directory - see below Archive Directory Shows when Archive the associated file to specified directory is selected.  Specify the directory where the archived file should be moved to.

Advanced Settings