---
sourceDocument: Yokohama Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/build-workflows

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Update Record activity

# Update Record activity {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Update Record activity

The Update Record activity in ServiceNow allows you to update a record with specified field values within a playbook.
This activity is available as a common activity and can be added by users with theadmin,playbook.admin, orpdauthorroles.
It enables automation and control over record updates, helping to streamline workflows and ensure accurate data updates.
Show full answer Show less  

## Inputs

To configure the Update Record activity, you set values for key inputs within the activity properties panel:

* **Label:** A title displayed on the activity and playbook card.
* **Description:** Information about the activity's usage or outcome.
* **Run condition:** Conditions that must be met for the activity or stage to run, built using prior activity data.
* **Start Rule:** Defines when the stage or activity starts, either at playbook start, after specific stages or activities, or with an optional delay.
* **Table:** Specifies the table containing the record to update.
* **Record:** Reference to the specific record to update.
* **Fields Template Value:** The field values that you want to change during the update.
* **Wait for user input:** Option to pause the playbook until user completion or skip, editable only by playbook.admin role.

Advanced inputs include assignment group and assigned user references to designate responsibility for the task, and fields to display after the update.

## Outputs

The activity outputs provide updated record data for use in subsequent playbook activities, including:

* **Table:** The name of the table containing the updated record.
* **Record Document ID:** Reference to the updated record.

## Design considerations

* **Create form views:** Use tailored form views to display only necessary fields for updating records, ensuring required fields and validation logic are included.
* **Sequence activities carefully:** Run non-interactive Update Record activities before interactive ones to avoid blocking dependent activities in the playbook.

This activity empowers ServiceNow customers to automate record updates efficiently within playbooks while providing flexibility in execution timing and user interaction, ensuring smooth and controlled workflow management.  
Update a record with the field values you specify.

## Roles and availability {#update-record-activity__section_pwq_rb5_kcb}

* This activity is available as a common activity. Users with the admin, playbook.admin, or pd_author can add this activity to a playbook.
{#update-record-activity__ul_mcq_1c5_kcb}

## Inputs {#update-record-activity__section_yb4_zq3_plb}

Open the activity properties panel and configure your activity to add values for the following inputs. If the input value varies, use the pill-picker to show where to get the value. To learn more about the pill-picker, see [Dot-walking examples](https://www.servicenow.com/docs/access?context=dot-walking-examples&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US). {#update-record-activity__table_ajt_sr3_plb__entry__3}{#update-record-activity__wait-process}

| Input | Type | Description |
|-|-|-|
| Label | String | Title to display as activity and playbook card. |
| Description | String | Information to display about activity usage or outcome. |
| Run condition | Condition Builder | Conditions that must be met to run an activity or stage. You can use data from prior activities to build conditions. Note: Show additional options to see this field. |
| Start Rule | Choice | Under ScheduleStart Rule, select a start rule for when your stage should start running: * When process starts: Your stage starts running as soon as the playbook starts. * After specific stages: Your stage starts running after specified stage(s) have finished running. {#update-record-activity__ul_f4z_nq1_ppb}Under Schedule \> Start Rule, select a start rule for when your activity should start running: <!-- --> * When stage starts: Your activity starts running as soon as its stage starts running. Your stage starts running when your playbook is triggered. * After specific activities: Your activity starts running after specified activities have finished running. {#update-record-activity__ul_zzc_3ls_m1c} |
| Start with delay | True/False | Option to wait for a duration of time before running an activity or stage. When enabled, this input displays the [Start with delay input properties](https://servicenow-prod.fluidtopics.net/ZO5_TxRewwK7XqnX5otC7A "Specify a duration of time to wait before running an activity or a stage whose start rule and conditions have been met. Give users time to act during automated playbooks. Give users time to wait for a specific date and time to complete actions."). Note: Show additional options to see this field. |
| Table | Table Name | Table containing the record to update. |
| Record | Reference | Reference to the record you want to update. |
| Fields | Template Value | Field values to change during record update. |
| Wait for user input | Choice | Option to pause the playbook until the end user manually completes or skips the activity. Only users with the playbook.admin role can edit this field. By default, the activity waits for user action or data before it completes. |
[ ]

{#update-record-activity__table_ajt_sr3_plb}

## Advanced inputs {#update-record-activity__section_bgh_1r3_plb}

After configuring the required inputs for your activity, you can also choose to configure additional inputs. In the side panel, select Show additional options to display these advanced inputs. For more information, see [Activity experience](https://servicenow-prod.fluidtopics.net/r014Lhz_11xoMRZZRHOzcA#activity-definitions__activity-experience). {#update-record-activity__table_cjj_sr3_plb__entry__3}

| Input | Type | Description |
|-|-|-|
| Assignment Group | Reference.Group \[sys_user_group\] | Group responsible for completing the task associated with the activity. Note: Show additional options to see this field. |
| Assigned To | Reference.User \[sys_user\] | User responsible for completing the task associated with the activity. Note: Show additional options to see this field. |
| Fields to show after update | String | Comma-separated list of fields to display for an updated record. |
[ ]

{#update-record-activity__table_cjj_sr3_plb}

## Outputs {#update-record-activity__section_unx_fr3_plb}

These outputs can provide data to other activities in your playbook. You can access this data as activity inputs when you configure your activity: {#update-record-activity__table_mv2_rr3_plb__entry__3}

| Output | Type | Description |
|-|-|-|
| Table | Table Name | Table containing updated record. |
| Record | Document ID | Reference to record updated. |
[ ]

{#update-record-activity__table_mv2_rr3_plb}

## Design considerations {#update-record-activity__section_td2_fr3_plb}

Create form views for activities that you want to render in a playbook
:   Use a form view to display only the fields your users need to update a record. Your
    view should display required fields or those fields validated by other business logic.
    See [View Management](https://www.servicenow.com/docs/access?context=view-management-overview&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US).

Run non-interactive activities before interactive activities
:   If an Update Record activity interactively gathers data from users, it prevents the playbook from starting any dependent activities. For example, an Update Record activity would prevent starting After Previous activities, which may be in other stages. Where possible, design your playbooks to run non-interactive activities before interactive activities that could block them.

*[\>]: and then