{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":4072,"path":"build-workflows/workflow-studio/create-record-activity.md","title":"Create Record activity","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create Record activity\n\nPause the playbook and prompt the end user to create a record in a form view. Use this activity to allow the end user to create a record. This activity requires you to configure the desired table for which record to create, and the desired form view that the end user will see when creating the record.\n\n## Roles and availability\n\nThis 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\nTable\n\n</td><td>\n\nTable Name\n\n</td><td>\n\nTable in which to insert new record.\n\n</td></tr><tr><td>\n\nCreate Record View\n\n</td><td>\n\nString\n\n</td><td>\n\nForm view to use for record creation. If you don't provide a form view, the system uses the default view. Use the **new tab** button \\[Omitted image \"new-tab-button.png\"\\] Alt text: a button that opens a new tabto open and edit a form view with Form Builder in a new Workflow Studio tab.**Note:** Many form views are not supported in Workspace.\n\n</td></tr><tr><td>\n\nTemplate Fields\n\n</td><td>\n\nTemplate Value\n\n</td><td>\n\nField values to set during record creation.\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 new record.|\n|Create Record View|String|Form view used for record creation.|\n|Record Created|Sys ID|Unique identifier of the record that this activity created.|\n\n## Design considerations\n\n-   **Create form views for activities that you want to render in a playbook during runtime.**\n\n    Use a form view to display only the fields your users need to create a record. Your view should display required fields or those fields validated by other business logic. See [View Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/view-management-overview.md).\n\n-   **Run non-interactive activities before interactive activities**\n\n    While a Create Record activity interactively gathers data from users, it prevents the playbook from starting any dependent activities. For example, a Create 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.\n\n\n"}}