Finish draft

Author: jpipkin1

blog-csoar/2025-04-21-content.md

@@ -28,6 +28,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
 * Added a confirmation dialog to alert users about pre-existing playbook drafts to avoid accidental overwriting while editing playbooks.
 * Implemented an alert popup to prevent accidental loss of unsaved changes when closing a node popup.
 * Added audit logs for failed nodes due to errors or exceptions during playbook execution.
+* Added the ability to enable or disable playbooks.
 
 ### Bug fixes
 

docs/platform-services/automation-service/automation-service-playbooks.md

@@ -226,16 +226,29 @@ Every time you publish a playbook, a new version of the playbook is retained. In
 
 <img src={useBaseUrl('img/platform-services/automation-service/playbook-versions.png')} alt="Playbook versions" style={{border:'1px solid gray'}} width="800"/>
 
-## Enable or disable a playbook
+## Enable or disable playbooks
 
-You can enable a playbook for use, or disable it to prevent it from being used in automations. Whether a playbook is enabled or disabled displays in the **Status** column: <br/><img src={useBaseUrl('img/platform-services/automation-service/playbook-status-enabled-disabled.png')} alt="Playbook status column" style={{border:'1px solid gray'}} width="800"/>
+You can enable playbooks for use in automations, or disable them to prevent them from being used. This gives you greater control over when a playbook can be run. If for example a playbook is causing a problem, such as exceeding your actions limit or sending too many emails, you could temporarily disable the playbook until you remedy the issue. 
 
-Status:
-* Enabled: <img src={useBaseUrl('img/platform-services/automation-service/playbook-enabled-symbol.png')} alt="Playbook enabled symbol" style={{border:'1px solid gray'}} width="40"/>
-* Disabled: <img src={useBaseUrl('img/platform-services/automation-service/playbook-disabled-symbol.png')} alt="Playbook disabled symbol" style={{border:'1px solid gray'}} width="40"/>
+When enabling or disabling playbooks, keep in mind:
+* Only published playbooks are enabled.
+* Disabled playbooks cannot be triggered automatically.
+* Deleted playbooks are set to disabled and remain so after restoration.
+* Cloned or imported playbooks are enabled by default, irrespective of the original playbook's status.
+* [Audit logs](/docs/platform-services/automation-service/automation-service-audit-logging/) are generated whenever playbooks are enabled or disabled manually. 
 
 
+### How to enable or disable a playbook
 
+To enable or disable a playbook, open the playbook and click the toggle.<br/><img src={useBaseUrl('img/platform-services/automation-service/playbook-enabled-toggle.png')} alt="Playbook enabled toggle" style={{border:'1px solid gray'}} width="400"/><br/><img src={useBaseUrl('img/platform-services/automation-service/playbook-disabled-toggle.png')} alt="Playbook disabled toggle" style={{border:'1px solid gray'}} width="400"/>
+
+The **Status** column shows whether a playbook is enabled <img src={useBaseUrl('img/platform-services/automation-service/playbook-enabled-symbol.png')} alt="Playbook enabled symbol" style={{border:'1px solid gray'}} width="30"/> or disabled <img src={useBaseUrl('img/platform-services/automation-service/playbook-disabled-symbol.png')} alt="Playbook disabled symbol" style={{border:'1px solid gray'}} width="30"/>.
+
+<img src={useBaseUrl('img/platform-services/automation-service/playbook-status-enabled-disabled.png')} alt="Playbook status column" style={{border:'1px solid gray'}} width="800"/>
+
+### Enable on publish
+
+By default, draft playbooks are disabled. When you click the **Publish** button at the bottom of the playbook window to publish a draft, the playbook is automatically enabled.<br/><img src={useBaseUrl('img/cse/automations-publish-playbook.png')} style={{border:'1px solid gray'}} alt="Publish the playbook" width="250"/>
 
 ## Playbook preferences