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 Page History

Version 1 Next »

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

Overview

Use a  Delete node to delete records on a selected 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.

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.

Advanced Settings

FieldDescription
Prioritise throughput over ordering

When this option is ticked records are processes 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

For links to all pages in this topic, see Understanding Actionflows. 


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