Merge branch 'main' into replace-reinvent-banner

Author: kimsauce

docs/platform-services/automation-service/app-central/integrations/incident-tools.md

@@ -7,8 +7,8 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
 
 <img src={useBaseUrl('/img/platform-services/automation-service/app-central/logos/incident-tools.png')} alt="incident-tools" width="100"/>
 
-***Version: 1.8  
-Updated: June 24, 2024***
+***Version: 1.9  
+Updated: Dec 5, 2025***
 
 :::sumo Cloud SOAR
 This integration is only for Cloud SOAR.
@@ -106,3 +106,4 @@ import AccessKey from '../../../../reuse/automation-service/access-key.md';
     * Search Incidents
     * Update Entity
 * June 24, 2024 (v1.8) - The **Field ID** and **Field Value** fields are now optional in the **Update Incident Fields** action.
+* December 5, 2025 (v1.9) - Added `closing_note` in output field of Get Incident action.

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

@@ -123,7 +123,7 @@ For examples of adding conditions to playbooks, see the [Cloud SIEM automation e
    * **Artifact fields**. Fields obtained from [incident artifacts](/docs/cloud-soar/incidents-triage/#incident-generation).
    * **Incident fields**. Fields obtained from [incidents](/docs/cloud-soar/settings/#incidents).
    * **Triage**. Fields obtained from [triage](/docs/cloud-soar/incidents-triage/#triage-field-settings).
-   * You can also manually enter a value, such as a string or numeric literal.<br/><img src={useBaseUrl('img/cse/automations-add-condition-node-2.png')} style={{border:'1px solid gray'}} alt="Get values for the condition" width="500"/>
+   * You can also manually enter a value, such as a string or numeric literal.<br/><img src={useBaseUrl('img/cse/automations-add-condition-node-new.png')} style={{border:'1px solid gray'}} alt="Get values for the condition" width="500"/>
 1. Under **Get value from a previous action**, select the value to feed into the condition. The example shows **IP Reputation V2** and **Playbook inputs** that came from the previous action. (The condition must be linked by a line to the previous action node to receive outputs from the action.) Click the options from the previous action and select which output type (for example, hashes, IP addresses, domains) to evaluate and add it to the condition.
 1. The selected output type will be displayed under **Condition 1**. Select which condition you would like for the output results to meet from the inequality operators below and click **Select a value** to define the condition.
 1. Now that **Condition 1** is defined, you can choose to filter your results further by selecting an **AND/OR** operator to define another condition.