<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Question from Playbook Optimization webinar: Field mapping in incident in Cortex XSOAR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/question-from-playbook-optimization-webinar-sub-playbook-quiet/m-p/494669#M906</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Reply by: &lt;/SPAN&gt;&lt;A href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/145971" target="_blank"&gt;&lt;SPAN&gt;@RVijay&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;1. This will not affect the main playbook as the output is still made available to the parent. Quiet mode suppresses the 'indexing' of inputs and outputs to improve it's performance, especially if the input or output size is large. So no real impact will be observerd with regards to the flow of the playbook. 2. Older incidents are not impacted by the change. Only incidents that were ingested after the change was made are affected.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 30 May 2022 10:28:45 GMT</pubDate>
    <dc:creator>rtsedaka</dc:creator>
    <dc:date>2022-05-30T10:28:45Z</dc:date>
    <item>
      <title>Question from Playbook Optimization webinar: Sub-Playbook quiet mode</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/question-from-playbook-optimization-webinar-sub-playbook-quiet/m-p/494668#M905</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Let's say we fix a sub playbook to run in quiet mode cos it's larger than 150KB. Will this affect the main playbook if it is dependent on the subplaybook output. Also will it fix all the older incidents that have already run ?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;** Note: this is a question from our&lt;A href="https://live.paloaltonetworks.com/t5/customer-success-webinars/customer-success-webinar-playbook-optimization-in-cortex-xsoar/ta-p/492705" target="_blank" rel="noopener"&gt; Customer Success Webinar: Playbook optimization in Cortex XSOAR&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;LI-PRODUCT title="Cortex XSOAR" id="Cortex_XSOAR"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 30 May 2022 10:31:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/question-from-playbook-optimization-webinar-sub-playbook-quiet/m-p/494668#M905</guid>
      <dc:creator>rtsedaka</dc:creator>
      <dc:date>2022-05-30T10:31:45Z</dc:date>
    </item>
    <item>
      <title>Re: Question from Playbook Optimization webinar: Field mapping in incident</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/question-from-playbook-optimization-webinar-sub-playbook-quiet/m-p/494669#M906</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Reply by: &lt;/SPAN&gt;&lt;A href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/145971" target="_blank"&gt;&lt;SPAN&gt;@RVijay&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;1. This will not affect the main playbook as the output is still made available to the parent. Quiet mode suppresses the 'indexing' of inputs and outputs to improve it's performance, especially if the input or output size is large. So no real impact will be observerd with regards to the flow of the playbook. 2. Older incidents are not impacted by the change. Only incidents that were ingested after the change was made are affected.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 30 May 2022 10:28:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/question-from-playbook-optimization-webinar-sub-playbook-quiet/m-p/494669#M906</guid>
      <dc:creator>rtsedaka</dc:creator>
      <dc:date>2022-05-30T10:28:45Z</dc:date>
    </item>
  </channel>
</rss>

