Skip to content

Save – saving the current record

The command "Save" saves the current record, with the same checks and business rules as a user pressing save. This page is for administrators who build actions that change records.

1. At a glance
Purpose Store the changes the action (or the user) made to the current record
Typical use After a series of updates, at the end of a background action, before leaving a record
Where in the editor Toolbar menu "Data" → "Save"
Needs a user interface No
Needs a current record Yes
Related Update Entity Record, Discard, quick action "Save"

2. Settings

The command has no settings of its own – only "Display Name", "Description" and "Execution Condition" on the tab "General" (see Actions).

3. Behaviour

  1. Without a current record, the command is skipped.
  2. The record is saved, together with related records the action created through it (for example with Create Related Record). Business rules that run before the save, required fields and validations are checked exactly as for a user.
  3. If the save is rejected, a user in the browser sees a dialog "Error occurred while saving" with the reasons – for example "Field(s) Customer must be filled in for Order O-1042" or "The value 'abc' is not valid for field Amount of Order O-1042". The action ends with an error.
  4. If the record was saved but a business rule that runs after the save failed, the user sees "The record was saved, but a follow-up rule failed" with the reason. The action continues.
  5. After a successful save, business rules that react on the save run – including actions they start in the background.

A save is final. A later command that fails does not undo it.

4. Examples

Several updates, one save. Three Update Entity Record commands without "Save", then one Save. Business rules that react on the save run once, not three times.

Save before an external call. Save, then HTTP Request to an ERP system that reads the order through the REST API – the ERP sees the stored state.

5. Limitations

  • In a background run, a rejected save is only visible in the protocol of the run and the log.