---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Playbook Experience

# Playbook Experience {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Understand how Playbook work in the ServiceNow AI Platform® to automate cross-functional processes and consolidate them into task-oriented views for your end users.
AllProcess AutomationWorkflow StudioPlaybooks is the design environment where playbook owners build playbooks. Meanwhile, the runtime experience is where end users, such as playbook agents, follow the playbook to complete a business process. To learn more about the Playbook designer, see [Playbook builder](https://servicenow-prod.fluidtopics.net/SG6l~MFlTYXsJfPQVx83ZQ "Playbooks is a component in Workflow Studio. Workflow Studio gives you a streamlined way to author, configure, and monitor playbooks, flows, subflows, actions, and decision tables in one place.").

## Runtime experience {#process-automation-designer-architecture-overview__section_jsh_hkh_ykb}

Workflow Studio produces these runtime components for Playbooks:  

Process executions
:   A process execution stores the details of running a playbook in a context record. You can use a process execution to troubleshoot and verify that playbooks run as expected.

Activity executions
:   An activity execution stores the details of running an activity instance in a
    context record. You can use an activity execution to troubleshoot and verify that playbooks run as expected.

Playbook runtime
: Playbook runtime is when a playbook runs for an agent or fulfiller. A playbook runs for agents only after Playbook Experience administrators configure how and where the playbook appears.  
During runtime for a playbook, your instance:

1. Evaluates any conditions specified in the trigger definition and processes the trigger.
2. Processes the [Events](https://servicenow-prod.fluidtopics.net/sJ0WAY0T1wqhPjps6xTkjw "Events are special records that the system uses to log when certain conditions occur and to take some kind of action in response to the conditions.") and starts running the playbook in the background.
3. Builds the automation plans from each activity into an entire process plan.
4. Runs the process plan for your playbook.
5. Stores the process execution information in the Process Execution \[sys_pd_context\] table.
6. Provides data for the running playbook view that agents and fulfillers experience.
{#process-automation-designer-architecture-overview__ol_klv_ynb_blb}  
Figure 1. Playbook processing

Your instance processes a playbook during runtime by evaluating trigger conditions, processing the event in the queue, building and running a process plan, storing process execution details, and providing data for the Playbook Experience.

## Data security and HTML sanitization {#process-automation-designer-architecture-overview__section_n4f_1hl_2qb}

Playbooks protects against cross-site
scripting and code injection by evaluating all string data for HTML markup. The system only
preserves HTML markup that is present in its inclusion list. All other HTML markup is
removed from string data.

The inclusion list supports these HTML elements and
attributes, which cannot be modified.  
{#process-automation-designer-architecture-overview__table-html-inclusion-list__entry__2}

| HTML element | Included Attributes |
|-|-|
| a | class, href, target, title |
| abbr | class, title |
| address | class |
| area | alt, class, coords, href, shape |
| article | class |
| aside | class |
| audio | autoplay, class, controls, loop, preload, src |
| b | class |
| bdi | class, dir |
| bdo | class, dir |
| big | class |
| blockquote | cite, class |
| br | class |
| caption | class |
| center | class |
| cite | class |
| code | class |
| col | align, class, span, valign, width |
| colgroup | align, class, span, valign, width |
| dd | class |
| del | class, datetime |
| details | class, open |
| div | class |
| dl | class |
| dt | class |
| em | class |
| emp | class |
| font | class, color, face, size |
| footer | class |
| h1 | class |
| h2 | class |
| h3 | class |
| h4 | class |
| h5 | class |
| h6 | class |
| header | class |
| hr | class |
| html |   |
| i | class |
| img | alt, class, height, src, title, width |
| input | aria-label, class, type, value |
| ins | class, datetime |
| li | class |
| mark | class |
| nav | class |
| ol | class |
| p | class |
| pre | class |
| s | class |
| section | class |
| small | class |
| span | class |
| sub | class |
| sup | class |
| svg | class |
| strong | class |
| style |   |
| table | align, border, class, valign, width |
| tag | class |
| tbody | align, class, valign |
| td | align, class, colspan, rowspan, valign, width |
| tfoot | align, class, valign |
| th | align, class, colspan, rowspan, valign, width |
| thead | align, class, valign |
| tr | align, class, rowspan, valign |
| tt | class |
| u | class |
| ul | class |
| video | autoplay, class, controls, height, loop, preload, src, width |
[Table 1. HTML inclusion list]

{#process-automation-designer-architecture-overview__table-html-inclusion-list}

*[\>]: and then