This page provides details of the properties for the save node, which is part of an actionflow.

Overview

Use a Save action node to insert, update or delete records for a selected table.

Sections on this page

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.

Create Save Stream Action pop-up Window

Field	Description
Name
Type	Auto InsertUpdate Insert Update Delete
Stream	Click the show list icon and Drag and drop it in from the repository

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

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.

Save requires a transactional table to be attached. Dragged in when you create it - listed in the Table property

The save node will make a change to a record in the table. Depends on the selected save Type.

For Auto Insert/Update - depends on the what is passed in through the incoming connection (todo-fiona: check this is right. original phrase was "provided with"

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. to display this node in the repository. to omit this node from the repository.
Type	Auto Insert/Update Insert or update records using the following condition: If the incoming connection passes in the primary key of an existing record, this save node updates the record in the attached table If the incoming connection does not pass in the primary key of an existing record, this save node inserts a new record. Insert Always insert a new record into the attached table Update Will always update a record for the attached table. For a record to update successfully a primary key must be provided. Delete Will always delete a record on the attached table. For a record to be deleted successfully a primary key must be provided.
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

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

Save Node