---
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


---

# Playbook activity state mapping

# Playbook activity state mapping {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Use playbook activity state mapping to override the status of a playbook
card.

## Overview {#playbook-activity-state-mapping__section_yrk_z5z_lnb}

A playbook card's state comes from the Activity State by default. Activity states come from
the Sub Flow or Flow Action powering the activity.

Activity Definition authors can specify a record to provide the status shown in playbook
cards. This record is referred to as an Experience Status Record. It is
specified within an Activity Definition's experience properties.

Any record from any table can be used as an Experience Status Record. Default activity
definitions use sys_flow_data records as their Experience Status
Record.
Figure 1. Activity States displayed in card view

## Default Activity States {#playbook-activity-state-mapping__section_u31_fpz_lnb}

{#playbook-activity-state-mapping__table_ew3_kqz_lnb__entry__2}

| Status | Flow State |
|-|-|
| Pending | Flow has not started |
| In Progress | Flow is running |
| Complete | Flow has finished |
| Skipped | Flow was skipped due to conditions |
| Error | Flow encountered an error |
[Table 1. Out-of-the-box Default Activity States in sys_flow_data record]

{#playbook-activity-state-mapping__table_ew3_kqz_lnb}  
Activity states are used in the following:

* Declarative Action conditions
* Activity Override conditions
* Animations
* Card visual experience
{#playbook-activity-state-mapping__ul_mvj_ssf_mnb}

## Exceptions {#playbook-activity-state-mapping__section_jrk_yrz_lnb}

Business logic doesn't always align one-to-one with the flow. The following are examples of exceptions:

* An agent clicks Skip on an instructional card. The flow displays as complete, but the business logic is skipped.
* An agent clicks Restart on a completed instructional card. The flow does not restart the flow, just update the Flow Data record.
* A flow may never complete if a task is waiting for input from an agent to restart a loop. The associated task is effectively complete in this state.
{#playbook-activity-state-mapping__ul_g3x_csz_lnb}
* **[Playbook activity state-mapping rules](https://servicenow-prod.fluidtopics.net/BoVpUD8qVv6sDbA6SNvGcA)**   
  Use activity state-mapping rules to control which activity state is shown in a card for a given experience status record.
* **[Playbook activity state-mapping permissions](https://servicenow-prod.fluidtopics.net/OpeYk5fzRO7YmukJ2SpQXA)**   
  User permissions must be assigned to allow agents to complete, skip, or restart activities in playbook using activity state mapping.

**Related concepts**   

* [Activity definitions](https://servicenow-prod.fluidtopics.net/r014Lhz_11xoMRZZRHOzcA "Activity definitions describe how the activities in your playbook get the data that they need when your playbook runs.")
* [Automation Assets](https://servicenow-prod.fluidtopics.net/mU389THCpCX6TcjWJLTNJg "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.")
* [Optional activities](https://servicenow-prod.fluidtopics.net/pJEY3EDh5wh5XlpPOIG19Q#optional-activities "Enable your agents and fulfillers to add additional activities as they go through a playbook.")  
**Related tasks**   

* [Add and configure a stage in a playbook](https://servicenow-prod.fluidtopics.net/Vk3iDYyg_Df62zD4oj~nDQ "Add and configure a stage in your playbook.")
* [Add and configure an activity in a playbook](https://servicenow-prod.fluidtopics.net/eH66_4Re8HXK8adZ1kzWiw "Add and configure an activity in your playbook.")
* [Decision activities](https://servicenow-prod.fluidtopics.net/4rX5cqI_FXRlYNq~tfDHiQ "Create and define branches with different conditions for different paths that an agent can follow in playbook.")
* [Parallel branches](https://servicenow-prod.fluidtopics.net/PNev5QskKuGUAmoIHUw0fQ "Add branches for activities and stages that run in parallel to another branch of activities and stages.")
* [Add dynamic inputs to an activity](https://servicenow-prod.fluidtopics.net/8XnLc2y4MM0hKIntwpZR5A "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.")  
**Related reference**   

* [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.")
* [Questionnaire activity](https://servicenow-prod.fluidtopics.net/0Zhk1Qtvq62no8BNvPsGbQ "Collects inputs from a user during a playbook run to use later in the playbook.")