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 13 Next »

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

Overview

Use a  Delete node to delete selected records from a table. Delete nodes will delete records that where the Primary Key for the selected record(s) match those on the specified table. 

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.

 Properties Tab

Parent Details

If this item is within or belongs to another, its parent name is shown here. See the Parent Details section on the Common Properties page for more details.

Basic Settings

FieldDescription
NameEnter the name for the action node.
Table

The table in which the records will be updated. This table must have a Period of Transactional. See Table.

Auto Save Attributes

 Enable to automatically delete unmapped attributes from the input, matched by the UID.

Mapped Attributes

FieldDescription
NameEnter the name for the attribute mapped to the Delete node.
Type

The data type of the attribute mapped to the Delete node. See Understanding Data Types.

File Tidy Up Settings

Where the selected table is a  File Table, 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.

FieldDescription
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

FieldDescription
Prioritise throughput over ordering

When this option is ticked records are processed in parallel to optimise performance. This means the order records are processed is nondeterministic.

When unticked (default), records are processed in the order they are provided.

Description

We recommend that you always enter a description to explain the purpose of this item.

 Security Tab

Access Permissions

See the Common Properties page, Access Permissions section.

 Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.

Sections on this page

Learn More


Terminology changes in progress

As part of the redesign of PhixFlow, we are changing the following terms:

dashboard → screen   
stream → table
stream attributes → attributes
stream item → record
stream set → recordset
stream view → view
stream item action → record-action 
stream action → table-action
driver class → database driver

  • No labels