This page provides details of the properties for the delete node. Overview
Use a | Insert excerpt |
|---|
| _action_delete |
|---|
| _action_delete |
|---|
| nopanel | true |
|---|
|
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. If you wish to purge records from your PhixFlow system entirely including Audit History see Bulk Delete Node 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. - The Primary Key of the selected records on the All Companies grid are mapped onto the Input Connection Point.
- 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 |
|---|
|
| Insert excerpt |
|---|
| _parent |
|---|
| _parent |
|---|
| nopanel | true |
|---|
|
Basic Settings| Field | Description |
|---|
| Name | Enter 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| Field | Description |
|---|
| 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. |
| Insert excerpt |
|---|
| _description |
|---|
| _description |
|---|
| nopanel | true |
|---|
|
| Insert excerpt |
|---|
| _access |
|---|
| _access |
|---|
| nopanel | true |
|---|
|
|