This page provides details of the properties for the 
Save action. This is a node in an actionflow.
Overview
Use a Save action node to insert, update or delete records for a selected table.
Example
In the actionflow above a user is saving values on an edit form (Company Edit Form) to a Company table. In this workflow all changes must be approved by a second colleague. All attributes on the edit form need to be saved and a Status attribute to manually set to 'Pending Approval', StatusUpdate to the current time and StatusUpdatedBy to the users name using a calculate node.
To automatically save all the attributes on the form all the user has to do is click 'Auto Save Attributes'. This automatically saves any attributes on the driving input form which link to the table on the save node. 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
When the save action 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.
- Internal: By default, PhixFlow automatically allocates a unique, numeric value to the primary key attribute.
- Sequence: Configure PhixFlow to allocate a value from your own sequence using the Primary Key Generator Sequence option. see Stream > Data Generation Options and Sequence.
Properties Tab
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.Parent Details
Basic Settings
| Field | Description |
|---|---|
| Name | Enter the name for the action node. |
| Show in the Repository | 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. |
| Type |
|
| Table | The table where the data is going to be updated. |
| Auto Save Attributes | If selected, this action will automatically save unmapped attributes from the driving input form or view, matched by id. If an attribute on the target table has not been mapped, the save action will check for a value by id (on a form the field will automatically be associated with the stream attribute if it has been added by dropping the stream attribute on the form). If there are multiple values for an attribute, the action will error. If there are no values for an attribute it will not be updated. |
Autosaving Attributes
If selected, this action will automatically save unmapped attributes from the driving input form or view, matched by id. If an attribute on the target table has not been mapped, the save action will check for a value by id (on a form the field will automatically be associated with the stream attribute if it has been added by dropping the stream attribute on the form). If there are multiple values for an attribute, the action will error. If there are no values for an attribute it will not be updated.
Attributes
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:
- to edit the attribute's properties, double-click an attribute; see View Attribute
- to delete an attribute, right-click and select
Delete
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
We recommend that you always enter a description to explain the purpose of this item.Description
See the Common Properties page, Access Permissions section.
Security TabAccess Permissions
See the Common Properties page, Audit Summary section.
Audit TabAudit Summary