<?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: Command modification in Cortex XSOAR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/question-from-playbook-optimization-webinar-command-modification/m-p/494667#M904</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Reply by: &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/152916"&gt;@RahulVijaydev&lt;/a&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;It is not possible to make configuration changes to a command's instance all across the board, and has to be performed individually. Searching for the name of the script/command from the playbooks search pane will list every playbook with an occurence of the script/command, and will allow you to make changes accordingly. ex. Searching for 'Sleep' will list all playbooks implementing the Sleep operation.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 31 May 2022 17:11:56 GMT</pubDate>
    <dc:creator>rtsedaka</dc:creator>
    <dc:date>2022-05-31T17:11:56Z</dc:date>
    <item>
      <title>Question from Playbook Optimization webinar: Command modification</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/question-from-playbook-optimization-webinar-command-modification/m-p/494664#M903</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Is it possible to modify all instances of a command? For instance, if we wanted to change the "Run without a worker" setting on all usages of sleep - is that possible? Or would I need to do it 1-by-1? Or even possible per playbook maybe with multi-select?&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"&gt; Customer Success Webinar: Playbook optimization in Cortex XSOAR&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&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:21:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/question-from-playbook-optimization-webinar-command-modification/m-p/494664#M903</guid>
      <dc:creator>rtsedaka</dc:creator>
      <dc:date>2022-05-30T10:21:54Z</dc:date>
    </item>
    <item>
      <title>Re: Question from Playbook Optimization webinar: Command modification</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/question-from-playbook-optimization-webinar-command-modification/m-p/494667#M904</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Reply by: &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/152916"&gt;@RahulVijaydev&lt;/a&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;It is not possible to make configuration changes to a command's instance all across the board, and has to be performed individually. Searching for the name of the script/command from the playbooks search pane will list every playbook with an occurence of the script/command, and will allow you to make changes accordingly. ex. Searching for 'Sleep' will list all playbooks implementing the Sleep operation.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 31 May 2022 17:11:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/question-from-playbook-optimization-webinar-command-modification/m-p/494667#M904</guid>
      <dc:creator>rtsedaka</dc:creator>
      <dc:date>2022-05-31T17:11:56Z</dc:date>
    </item>
  </channel>
</rss>

