Save Node
- Sarah Gibson (Unlicensed)
- Zoe Baldwin
- Anthony George
This page provides details of the properties for the save node, which is part of an actionflow. Use a Save node to insert and update records for a selected table. By default, Autosave Attributes is enabled, this saves any attributes on the driving input form that link to the table on the save node. Specific attributes can be overridden manually by specifying the attributes, or if Autosave Attributes is not enabled the Save node will only save attributes which are mapped to it and ignore any that have not been included. A Save node must be attached to a table with a Type of Transactional. In the actionflow instance illustrated in the screenshot above, an application has a Company Edit Form. When the application user makes a change and clicks the button, the actionflow runs. When the save node is inserting a new record to the table, PhixFlow allocates a unique primary key value to the record. How PhixFlow allocates a value is determined by the Table properties → Advanced → Primary Key Generator. 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. An application can have many actionflows, and an individual actionflow can have many nodes. This can lead to many items being listed under Actionflow in the repository. Use this option to omit the node from the repository. to display this node in the repository. to omit this node from the repository. The table in which the records will be updated. This table must have a Period of Transactional. Tick to save unmapped attributes from the driving input form or view, matched by identifier. A list of attributes to be updated manually. Click to show the list of attributes for the table. Drag the attributes you want to add to the save node into this list. In the list: Attributes not added to this list will not be changed unless 'Auto Save Attributes' is ticked. If a record is being inserted and an attribute is not present in the save node, the default value for this field will be _NULL When enabled, records are processed in parallel to optimise performance. This means the order records are processed is nondeterministic. When disabled (default), records are processed in the order they are provided. We recommend that you always enter a description to explain the purpose of this item. See the Common Properties page, Access Permissions section. See the Common Properties page, Audit Summary section.Overview
Example
This means if any additional fields are added to the backing table and input form they do not need to be mapped to the save node.Allocating Primary Key Values to New Records
Properties Tab
Parent Details
Basic Settings
Field Description Name Enter the name for the action node. Show in the Repository Type
Insert or update records using the following condition:
Always insert a new record into the attached table
Will always update a record for the attached table. For a record to update successfully a primary key must be provided.Table Auto Save Attributes Mapped Attributes
Advanced Settings
Field Description Prioritise throughput over ordering Description
Security Tab
Access Permissions
Audit Tab
Audit Summary
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