Two Step Instruction activity
Summarize
Summary of Two Step Instruction activity
The Two Step Instruction activity in the Yokohama release enables you to display different messages to end users based on the current state of the activity: initial (in progress), skipped, or completed. This helps communicate clear status updates within playbooks, enhancing user understanding and engagement.
Show less
Key Features
- State-based Messaging: Configure distinct messages for initial, skipped, and completed states to guide end users appropriately.
- Role Availability: Accessible to users with admin, playbook.admin, or pdauthor roles for adding to playbooks.
- Input Configuration: Inputs include labels, descriptions, run conditions, scheduling rules, and optional delay settings—all configurable via the activity properties panel.
- Scheduling Flexibility: Activities and stages can be triggered based on playbook start, completion of specific stages or activities, and can include start delays.
- Advanced Inputs: Assignment group and assigned user can be specified to designate responsibility for the task associated with the activity.
- Output Data: The activity outputs a reference to the related task record, which can be used as input in subsequent activities within the playbook.
Practical Use for ServiceNow Customers
By incorporating this activity into your playbooks, you can provide end users with clear, contextual messages that correspond to the activity's progress, skipped status, or completion. This improves communication and task tracking during playbook execution. The flexible scheduling and assignment options allow you to tailor the workflow to your operational needs, ensuring tasks are started and owned appropriately. Additionally, outputs from this activity can feed into downstream processes, supporting integrated and automated playbook designs.
Display a different message to end users based on the current activity state. You can specify an initial state message, a skipped state message, and a completed state message.
Roles and availability
- This activity is available as a common activity. Users with the admin, playbook.admin, or pd_author 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. |
| Initial Message | String | Message text to display to end users when the activity state is In Progress. |
| Completed Message | String | Message text to display to end users when the activity state is Completed. |
| Skipped Message | String | Message text to display to end users when the activity state is Skipped. |
Advanced inputs
| Input | Type | Description |
|---|---|---|
| Assignment Group | Reference.Group [sys_user_group] | Group responsible for completing the task associated with the activity. Note: Show additional options to see this field. |
| Assigned To | Reference.User [sys_user] | User responsible for completing the task associated with the activity. Note: Show additional options to see this field. |
Outputs
| Output | Type | Description |
|---|---|---|
| Record | Reference.Task[task] | Reference to the record associated with the activity. |