> For the complete documentation index, see [llms.txt](https://docs.work-relay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.work-relay.com/processes/process-actions/process-actions-types/update-records.md).

# Update Records

### Generic Process Action properties

This action has generic properties, as other process actions:

* **Name** - give action a name in order to search for it easy, otherwise system will use ID of this Action.
* **Step** - the step action is added at. This property can't be edited manually, but it will be updated if move this action to other step or connector.
* **Type** - main property which determines what Action will do and it's configuration. Once action is created, type can't be changed.
* **Status** - you can activate or deactivate an action temporary (e.g., for debug).
* **Start Type** - can be set to "Before step" or "After step". 

{% hint style="info" %}
This option is available only when action is added to the step. If action is added to a connector, it will be executed like "After step", where step is the outgoing step of this connector.
{% endhint %}

* **Execute** - specify if Action will be executed always or when some conditions are matched.
* **Description** - used internally only for admin's goals.

### Overview

**Update Record** action allows to change a record or a bunch of records.

### Configuration

* Select necessary object in Context Object Type. 

{% hint style="info" %}
This is not mandatory, but can be useful - e.g., if you want to update records with field values based on another record shown in current form.
{% endhint %}

* Set **Action Type** = "Update Records". 
* Select the **Object** **Name** - this will be an object which you will update records for.
* Select **fields** you need to be updated.

{% hint style="warning" %}
Some records can have required fields and these fields can be empty (e.g, they became required later than records were created). In this case "Update Records" action must update these fields too, otherwise system will fail it.
{% endhint %}

* Fill in **value** for each field. You can use static values by default. Switch to Advanced mode to use Merge Fields or [formulas](/automations/functions-and-formulas/introduction-and-usage.md) to populate values (see more info on Merge Fields and Formulas at [Working with Context objects](/automations/global-actions-and-action-groups/basics/working-with-context-objects.md) and [Working with Functions](/automations/functions-and-formulas/introduction-and-usage.md).
* Populate **Conditions** that should be matched by records. If do not specify conditions, ALL available records will be updated in the same way.

{% hint style="info" %}
Salesforce automatically restrict number of bulk updates to 100 records, if do not set limits.
{% endhint %}

* Specify **Conditions Logic** if needed.
* Specify **Limit** of records to update in one time. If set too big value, you may undergo system limitations.

<figure><img src="/spaces/kkIfnKKNSULyGZ085PIG/files/xqgwrDvKiWh0j8B6UNUu" alt=""><figcaption></figcaption></figure>

In the example at the picture above action will update Type and Rating fields in these records:

<img src="/spaces/kkIfnKKNSULyGZ085PIG/files/3Voc0WQWe0aw9TpDsBn4" alt="" class="gitbook-drawing">

### **Configure background execution**

* Check **Execute in background** if you need to execute this action in other context than current user operation. See more info at [How to use "Execute in Background" feature](/automations/global-actions-and-action-groups/using-actions/how-to-use-execute-in-background-feature.md). If check this option, the new field will appear:
  * **With gap**: by default it is 0, but can be set as an integer number of minutes. This field specifies interval before action execution (for repeated actions - before each iteration).

<figure><img src="/spaces/kkIfnKKNSULyGZ085PIG/files/GVqJCT2TzF9GaJFVuUd4" alt=""><figcaption></figcaption></figure>