Add Dynamic Inputs to an Activity
-
- UpdatedFeb 1, 2024
- 3 minutes to read
- Washington DC
- Process Designer
Add Dynamic Inputs to an Activity
Configure your activity to show a certain set of fields based on the value of another input, such as a selected catalog item, selected decision table, or even a REST API response.
Before you begin
Role required: pd_admin, pd_author, action_designer, flow_designer, admin
- In the ServiceNow AI Platform, you will create a new data definition for the dynamic input fields you want to add to an activity.
- In Workflow Studio, you will create a data gathering action.
- Still in Workflow Studio, you will create a subflow or another action with a dynamic input to consume the first action. This subflow or new action creates a JSON schema that represents the field(s) you want to add to an activity.
- In the ServiceNow AI Platform, you will create an activity definition using the subflow or action with the dynamic input.
Once your activity definition is created, Playbooks authors can add and configure activities with the dynamic inputs.
About this task
A dynamic input is an input that changes based on another input. In Workflow Studio Playbooks, you can present multiple dynamic inputs based on another input.
Example
- The first input required is for the Catalog Item field.
- A user selects iPad mini in the Catalog item field.
- Two (2) additional fields for color and storage options appear in response to the user selecting an iPad mini as the Catalog Item.
Procedure
On this page
Related Content
- Add and configure a stage in a playbook
Add and configure a stage in your playbook.
- Activity definitions
Activity definitions describe how the activities in your playbook get the data that they need when your playbook runs.
- Add and configure an activity in a playbook
Add and configure an activity in your playbook.
- Automation Assets
Include all automation assets in the activity picker to add a subflow, flow, or action directly to your playbook without having to create an activity definition.
- Start with delay input properties
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.
- Optional activities
Enable your agents and fulfillers to add additional activities as they go through a playbook.
- Decision activities
Create and define branches with different conditions for different paths that an agent can follow in playbook.
- Parallel branches
Add branches for activities and stages that run in parallel to another branch of activities and stages.