This action converts a data structure to a database record and updates the record in a database table.

Triggers

<Record> (non-repetitive trigger [required]): The record to update (a data structure with the record's new fields).

The database table is identified by the tableName property of the data type of <Record>.

The structure of the database table is automatically inferred from the structure of the added record (to learn more on the way data structures are saved as database records, refer to Insert).

<Data Source> (non-repetitive trigger [not required]): Name of data source to use (if different from the default data source; see Connecting to an External Database).

<Table Name> (non-repetitive trigger [not required]): Name of the database table (if different from the tableName property of the data type of <Record>).

<Auto Commit> (non-repetitive Boolean trigger [not required]): Indication whether to interact with the database in auto-commit mode.

If <Auto Commit> exists and a Yes value is received, the database action is performed in auto-commit mode, regardless of any active transaction (see Database Transaction Support in Tersus).

Exits [none required]

<Updated> (non-repetitive exit [not required]): The input data structure, in case the record has been updated in the table.

<Not Found> (non-repetitive exit [not required]): The input data structure, in case the record has not been updated (as it had not existed in the table in the first place).

Notice: The two exits represent two mutually exclusive possibilities: <Updated> is activated only if the record has been updated in the table; <Not Found> is activated only if it has not been updated. You can use the action with just one of the exits (if there is only one case that is interesting) or with both exits. You can also use the action with none of them (if none of the exits exists, you can, but not have to, add a <Done> empty exit, which will be activated in both cases).

"Approve Requisition" (at the end of stage 6 of the tutorial):