Create Record activity
Summarize
Summary of Create Record activity
The Create Record activity in ServiceNow's Process Automation Designer allows users to pause a playbook and prompt end users to create a record in a specified form view. This activity is essential for allowing users to input data directly into a designated table, enhancing workflow interactivity and data collection.
Show less
Key Features
- Role Availability: Accessible to users with admin, pdadmin, or pdauthor roles.
- Inputs Configuration: Users can configure inputs such as:
- Label: Title displayed for the activity.
- Description: Information regarding the activity's usage.
- Run Condition: Conditions that must be met for the activity to run.
- Start Rule: Determines when the stage or activity begins.
- Table: Specifies the table where the new record will be inserted.
- Create Record View: The form view used for creating the record.
- Template Fields: Values assigned during record creation.
- Outputs: Provides outputs including the table name, form view used, and the unique identifier (Sys ID) of the created record, which can be utilized in subsequent activities.
Key Outcomes
By effectively using the Create Record activity, users can create tailored form views that display only necessary fields, improving user experience and data accuracy. It is important to design playbooks to execute non-interactive activities before this interactive step to avoid blocking dependent activities, ensuring smooth workflow progression.
Pause 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.
Roles and availability
- This activity is available as a common activity. Users with the admin, pd_admin, or pd_author role can add this activity to a playbook.
Inputs
| 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 , select a start rule for when your stage should start running:
|
| 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. Note: Show additional options to see this field. |
| Table | Table Name | Table in which to insert new record. |
| Create Record View | String | Form 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 Note: Many form views are not supported in Workspace. |
| Template Fields | Template Value | Field values to set during record creation. |
Outputs
| Output | Type | Description |
|---|---|---|
| Table | Table Name | Table containing new record. |
| Create Record View | String | Form view used for record creation. |
| Record Created | Sys ID | Unique identifier of the record that this activity created. |
Design considerations
- Create form views for activities that you want to render in a playbook during runtime.
- 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.
- Run non-interactive activities before interactive activities
- 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.