--- sourceDocument: Yokohama Build workflows sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/build-workflows Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Build workflows ft:clusterId : - crworkflow bundleId : - crworkflow workflow : - Creator --- # Two Step Instruction activity # Two Step Instruction activity {#ariaid-title1} Release version: Yokohama Updated January 30, 2025 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Two Step Instruction activity The Two Step Instruction activity in the Yokohama release enables you to display customized messages to end users based on the current state of an activity within a playbook. You can specify different messages for the initial (In Progress), skipped, and completed states, enhancing communication clarity during playbook execution. Show full answer Show less ## Key Features * **State-Based Messaging:** Define distinct messages for activity states---In Progress, Completed, and Skipped---to guide or inform end users appropriately. * **Flexible Scheduling:** Configure start rules at both the stage and activity levels, enabling activities to start when the process or stage begins, or after specific stages or activities complete. * **Conditional Execution:** Use condition builder inputs to set precise criteria that must be met for an activity or stage to run, utilizing data from prior activities. * **Start Delay Option:** Optionally delay the start of an activity or stage by a specified duration to better control timing within playbooks. * **Assignment Configuration:** Assign ownership by specifying an Assignment Group or an individual Assigned To user responsible for completing the task linked to the activity. * **Input Value Flexibility:** Use the pill-picker feature to dynamically source input values, supporting complex playbook logic and data retrieval. ## Outputs The activity provides a reference output to the associated task record, enabling other playbook activities to access and utilize this data for downstream processes. ## Practical Application for ServiceNow Customers This activity allows you to enhance user experience by providing clear, state-dependent instructions during playbook execution. It supports conditional and scheduled execution, enabling you to design precise workflows that align with your organizational processes. Proper configuration of assignment ensures task accountability, while output references facilitate seamless integration with subsequent playbook activities. 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 {#two-step-instruction-activity__section_pwq_rb5_kcb} * This activity is available as a common activity. Users with the admin, playbook.admin, or pd_author can add this activity to a playbook. {#two-step-instruction-activity__ul_mcq_1c5_kcb} ## Inputs {#two-step-instruction-activity__section_yb4_zq3_plb} Open 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://www.servicenow.com/docs/access?context=dot-walking-examples&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US). {#two-step-instruction-activity__table_ajt_sr3_plb__entry__3} | 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 ScheduleStart 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. * After specific stages: Your stage starts running after specified stage(s) have finished running. {#two-step-instruction-activity__ul_f4z_nq1_ppb}Under Schedule \> 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. * After specific activities: Your activity starts running after specified activities have finished running. {#two-step-instruction-activity__ul_zzc_3ls_m1c} | | 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](https://servicenow-prod.fluidtopics.net/ZO5_TxRewwK7XqnX5otC7A "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."). 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. | [ ] {#two-step-instruction-activity__table_ajt_sr3_plb} ## Advanced inputs {#two-step-instruction-activity__section_bgh_1r3_plb} After configuring the required inputs for your activity, you can also choose to configure additional inputs. In the side panel, select Show additional options to display these advanced inputs. For more information, see [Activity experience](https://servicenow-prod.fluidtopics.net/r014Lhz_11xoMRZZRHOzcA#activity-definitions__activity-experience). {#two-step-instruction-activity__table_cjj_sr3_plb__entry__3} | 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. | [ ] {#two-step-instruction-activity__table_cjj_sr3_plb} ## Outputs {#two-step-instruction-activity__section_unx_fr3_plb} These outputs can provide data to other activities in your playbook. You can access this data as activity inputs when you configure your activity: {#two-step-instruction-activity__table_mv2_rr3_plb__entry__3} | Output | Type | Description | |-|-|-| | Record | Reference.Task\[task\] | Reference to the record associated with the activity. | [ ] {#two-step-instruction-activity__table_mv2_rr3_plb} *[\>]: and then