{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":3963,"path":"build-workflows/workflow-studio/automated-update-record-activity.md","title":"Automated Update Record activity","bundle":null,"doc_type":null,"release":"australia","body":"\n# Automated Update Record activity\n\nUpdate a record without pausing the playbook to ask for user input. When the activity runs, it immediately updates the record and continues to the next activity in the playbook. The record must meet server-side validation rules such as data policies, business rules and dictionary-defined mandatory fields but ignores UI policies.\n\n## Roles and availability\n\n-   This activity is available as a common activity. Users with the admin, playbook.admin, or pd\\_author can add this activity to a playbook.\n\n## Inputs\n\nOpen 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/dot-walking-examples.md).\n\n<table id=\"table_ajt_sr3_plb\"><thead><tr><th>\n\nInput\n\n</th><th>\n\nType\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nLabel\n\n</td><td>\n\nString\n\n</td><td>\n\nTitle to display as activity and playbook card.\n\n</td></tr><tr><td>\n\nDescription\n\n</td><td>\n\nString\n\n</td><td>\n\nInformation to display about activity usage or outcome.\n\n</td></tr><tr><td>\n\nRun condition\n\n</td><td>\n\nCondition Builder\n\n</td><td>\n\nConditions 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.\n\n</td></tr><tr><td>\n\nStart Rule\n\n</td><td>\n\nChoice\n\n</td><td>\n\nUnder **Schedule** &gt; **Start 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.\n-   **After specific stages**: Your stage starts running after specified stage\\(s\\) have finished running.\n\nUnder Schedule &gt; 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.\n-   **After specific activities**: Your activity starts running after specified activities have finished running.\n\n</td></tr><tr><td>\n\nStart with delay\n\n</td><td>\n\nTrue/False\n\n</td><td>\n\nOption 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/start-with-delay-properties.md).**Note:** Select **Show additional options** to see this field.\n\n</td></tr><tr><td>\n\nRecord\n\n</td><td>\n\nReference\n\n</td><td>\n\nReference to the record you want to update.\n\n</td></tr><tr><td>\n\nTable\n\n</td><td>\n\nTable Name\n\n</td><td>\n\nTable containing the record to update.\n\n</td></tr><tr><td>\n\nFields\n\n</td><td>\n\nTemplate Value\n\n</td><td>\n\nField values to change during record update.\n\n</td></tr></tbody>\n</table>## Outputs\n\nThese outputs can provide data to other activities in your playbook. You can access this data as activity inputs when you configure your activity:\n\n|Output|Type|Description|\n|------|----|-----------|\n|Table|Table Name|Table containing updated record.|\n|Record|Reference.Task\\[task\\]|Reference to record updated.|\n\n"}}