---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Update Record activity

# Update Record activity {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](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 enables you to update a specific record in a ServiceNow table with the field values you specify.
It is a common activity available to users with theadmin,playbook.admin, orpdauthorroles, and can be added to a playbook to automate record updates within your processes.
Show full answer Show less  

## Configuration Inputs

To configure the Update Record activity, you specify several key inputs through the activity properties panel:

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

Advanced inputs include assigning groups or users responsible for the task and specifying which fields to display after the update.

## Outputs

The activity outputs include references to the updated record and its table, which can be used as inputs for subsequent activities in the playbook, enabling seamless data flow.

## Design Considerations

* **Form Views:** Use tailored form views to display only necessary fields for updating records, ensuring users see relevant information and required fields.
* **Activity Sequencing:** To avoid blocking dependent activities, configure non-interactive Update Record activities to run before interactive ones that require user input.

## Practical Benefits

This activity helps automate updates to records within your workflows, improving efficiency and accuracy. By configuring conditions, timing, and user interactions, you can control when and how records are updated, providing flexibility and ensuring your processes reflect real-time data changes.  
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=australia&pubname=australia-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: Select 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://www.servicenow.com/docs/EdInaaLAHZCnrBcJbs96Lw "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: Select 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://www.servicenow.com/docs/aEvbv54ObgcCjjhXabvx8w#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: Select Show additional options to see this field. |
| Assigned To | Reference.User \[sys_user\] | User responsible for completing the task associated with the activity. Note: Select 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=australia&pubname=australia-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