Actions
SaveTo Database Action
Save data to a Database table.
The SaveToDatabase Action stores each submission data as a new record in a local or external Database Table. Use it to store or log submissions.
Settings
| Setting | Description | Required |
|---|---|---|
| Database | The name of the database to which to connect. | ✓ |
| Table | The name of the database Table to which to connect. | ✓ |
| Content | The mapping configuration of the submission data to the table columns. | ✓ |
| Custom Connection | Should the connection be manually inputed instead of inherited from the system. |
Common Settings
| Validation | Description |
|---|---|
| Action Name | The name to reference this action. |
| Status | Defines if the action is enabled or disabled. |
| Execution | A list of conditions that must be met in order for the action to be executed. |
Connection
The connection to the Database is by default system inherited with the possibility for manual override.
| Setting | Description |
|---|---|
| Host | The server host IP or address to which to connect, e.g. 127.0.0.1. |
| Port | The port to use for the connection, e.g. 3306. |
| Username / Password | The username & password which to use for the connection. |
Update Record
When the Update Record setting is enabled the Submission Data will override an existing table record which will be determined by the association configuration. If no associated record is found, a new record will be appended instead.
| Setting | Description | Dynamic | Required |
|---|---|---|---|
| Update Record | Should a record be updated instead of appended. | ||
| Associative Key | The table column key that will be used to associate the record. | ✓ | |
| Associative Value | The table column value that will be used to associate the record. | ✓ | ✓ |
An example to understand the association is to think of a Users Table with an ID column as its primary key. In such a scenario, the submission data should contain the user_id value representing the user row being updated, the Associative Key should be set as ID, and the Associative Value mapped to the Form Submission user_id.
Mapping
Once the table has been chosen, its columns will appear in the Content field ready to be mapped, being the column configuration pre-established by the table schema. The mapping will determine what value will be saved at what column of the record that is being saved or updated.
Not all columns require a value, in fact, mapping is disabled by default and must be enabled for each column independently. Once enabled, the value can be inputted manually or dynamically with the use of the Dynamic Workflow.
| Setting | Description | Dynamic |
|---|---|---|
| Value | The value that will be mapped to the column. | ✓ |
Integration
- Create a Form Area and access it Settings Panel.
- Add a SaveToDatabase action and fulfill the required settings.