{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":4280,"path":"build-workflows/workflow-studio/playbook-activity-state-mapping.md","title":"Playbook activity state mapping","bundle":null,"doc_type":null,"release":"australia","body":"\n# Playbook activity state mapping\n\nUse playbook activity state mapping to override the status of a playbook card.\n\nA playbook card's state comes from the Activity State by default. Activity states come from the Sub Flow or Flow Action powering the activity.\n\nActivity Definition authors can specify a records 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.\n\n\\[Omitted image \"activity-definition-tables-records.png\"\\] Alt text: Tables and records for an activity definition\n\nAny 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.\n\n\\[Omitted image \"playbook-activity-card-states.png\"\\] Alt text: Playbook activity states shown in card view\n\n## Default Activity States\n\n|Status|Flow State|\n|------|----------|\n|Pending|Flow has not started|\n|Ready|Flow is|\n|In Progress|Flow is running|\n|Complete|Flow has finished|\n|Skipped|Flow was skipped due to conditions|\n|Error|Flow encountered an error|\n|Canceled|Flow was canceled|\n\nActivity states are used in the following:\n\n-   Declarative Action conditions\n-   Activity Override conditions\n-   Animations\n-   Card visual experience\n\n## Exceptions\n\nBusiness logic doesn't always align one-to-one with the flow. The following are examples of exceptions:\n\n-   An agent clicks **Skip** on an instructional card. The flow displays as complete, but the business logic is skipped.\n-   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.\n\n-   **[Playbook activity state-mapping rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/playbook-activity-state-mapping-rules.md)**  \nMap playbook activity states to states from the given experience record.\n-   **[Playbook activity state-mapping permissions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/playbook-act-state-permissions.md)**  \nUser permissions must be assigned to allow agents to complete or skip activities in playbook using activity state mapping.\n\n**Parent Topic:**[Stages and activities](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/process-automation-designer-lanes-activities.md)\n\n"}}