<?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 Identify Manual Cases Using Filter - Layout Rules in Cortex XSIAM Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/identify-manual-cases-using-filter-layout-rules/m-p/1244287#M290</link>
    <description>&lt;P&gt;Hello Livecomm,&lt;/P&gt;
&lt;P&gt;I am working on the XSIAM platform and I want to provide a default layout for cases that are manually opened. The classic fields that contain this info such as _product and tags cannot be filtered on.&lt;/P&gt;
&lt;P&gt;Does anyone have a solution for this?&lt;/P&gt;
&lt;P&gt;Many thanks,&lt;/P&gt;
&lt;P&gt;MSysec&lt;/P&gt;
&lt;P&gt;&lt;LI-PRODUCT title="Cortex XSIAM" id="Cortex_XSIAM"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 21 Dec 2025 08:35:27 GMT</pubDate>
    <dc:creator>michaelsysec242</dc:creator>
    <dc:date>2025-12-21T08:35:27Z</dc:date>
    <item>
      <title>Identify Manual Cases Using Filter - Layout Rules</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/identify-manual-cases-using-filter-layout-rules/m-p/1244287#M290</link>
      <description>&lt;P&gt;Hello Livecomm,&lt;/P&gt;
&lt;P&gt;I am working on the XSIAM platform and I want to provide a default layout for cases that are manually opened. The classic fields that contain this info such as _product and tags cannot be filtered on.&lt;/P&gt;
&lt;P&gt;Does anyone have a solution for this?&lt;/P&gt;
&lt;P&gt;Many thanks,&lt;/P&gt;
&lt;P&gt;MSysec&lt;/P&gt;
&lt;P&gt;&lt;LI-PRODUCT title="Cortex XSIAM" id="Cortex_XSIAM"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 21 Dec 2025 08:35:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/identify-manual-cases-using-filter-layout-rules/m-p/1244287#M290</guid>
      <dc:creator>michaelsysec242</dc:creator>
      <dc:date>2025-12-21T08:35:27Z</dc:date>
    </item>
    <item>
      <title>Re: Identify Manual Cases Using Filter - Layout Rules</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/identify-manual-cases-using-filter-layout-rules/m-p/1247940#M337</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/209373"&gt;@michaelsysec242&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Greetings for the day.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In Cortex XSIAM, you can provide a default or specific layout for manually opened cases by utilizing &lt;STRONG&gt;Incident Layout Rules&lt;/STRONG&gt; in conjunction with &lt;STRONG&gt;Custom Incident Fields&lt;/STRONG&gt;. Since certain system fields like tags or &lt;CODE&gt;_product&lt;/CODE&gt; may have filtering limitations in the layout rule engine or exhibit known UI issues, the most reliable solution is to create a dedicated custom field to trigger your desired layout.&lt;/P&gt;
&lt;H4&gt;&amp;nbsp;&lt;/H4&gt;
&lt;H4&gt;Recommended Solution: Custom Field Workaround&lt;/H4&gt;
&lt;P&gt;To apply a specific layout to manual cases when system filters are not working as expected, follow these steps:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;1. Create a Custom Incident Field&lt;/H4&gt;
&lt;P&gt;Create a field that will act as the trigger for your manual case layout.&lt;/P&gt;
&lt;P&gt;Navigate to:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Cases &amp;amp; Issues → Case Configuration → Incident Fields&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Create a new field (for example, &lt;CODE&gt;Manual_Case_Type&lt;/CODE&gt;) with a type such as:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;Short Text, or&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Single Select&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;This field will be used in your layout rule condition.&lt;/P&gt;
&lt;H4&gt;&amp;nbsp;&lt;/H4&gt;
&lt;H4&gt;2. Build the Custom Incident Layout&lt;/H4&gt;
&lt;P&gt;Design the layout you want to display for manually created cases.&lt;/P&gt;
&lt;P&gt;Navigate to:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Cases &amp;amp; Issues → Case Configuration → Incident Layouts&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;Create a new layout.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Add the sections, tabs (such as Key Assets, Alerts &amp;amp; Insights), and fields you want to display.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;You can hide or reorder default tabs such as the Incident War Room or Timeline if needed.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H4&gt;&amp;nbsp;&lt;/H4&gt;
&lt;H4&gt;3. Define an Incident Layout Rule&lt;/H4&gt;
&lt;P&gt;Create the rule that applies your layout based on your custom field.&lt;/P&gt;
&lt;P&gt;Navigate to:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Cases &amp;amp; Issues → Case Configuration → Incident Layout Rules&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;Create a new rule.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Set the condition to use your custom field (for example, &lt;CODE&gt;Manual_Case_Type&lt;/CODE&gt; equals &lt;CODE&gt;Manual&lt;/CODE&gt;).&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Select your custom layout as the layout to apply.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;Important:&lt;/STRONG&gt;&lt;BR /&gt;Layout rules are evaluated from top to bottom. The system applies the first matching rule, so ensure your new rule is ordered correctly in the list.&lt;/P&gt;
&lt;H4&gt;&amp;nbsp;&lt;/H4&gt;
&lt;H4&gt;4. Populate the Field During Case Creation&lt;/H4&gt;
&lt;P&gt;When manually opening a case, make sure the trigger field is populated.&lt;/P&gt;
&lt;P&gt;If the custom field is included in the default case creation form:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;Set it to the value defined in your rule (for example, &lt;CODE&gt;Manual&lt;/CODE&gt;).&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;The correct layout will be applied immediately upon case creation.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H4&gt;&amp;nbsp;&lt;/H4&gt;
&lt;H4&gt;Context on Field Limitations:&lt;/H4&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Tags / Data Source:&lt;/STRONG&gt; Data source information is often stored as tags, which may not be consistently supported for filtering in certain configuration engines or datasets.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Filtering Issues:&lt;/STRONG&gt; There are known UI issues in some versions where tag-based filtering may not populate correctly or return expected results.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Incident Name Field:&lt;/STRONG&gt; Although layout rules can be based on Incident Name, some versions have exhibited inconsistent behavior with this field, making custom fields a more stable and predictable option.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you feel this has answered your query, please let us know by clicking like and on&amp;nbsp;&lt;STRONG&gt;"mark this as a Solution".&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;S. Subashkar Sekar&lt;/P&gt;</description>
      <pubDate>Wed, 11 Feb 2026 14:15:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/identify-manual-cases-using-filter-layout-rules/m-p/1247940#M337</guid>
      <dc:creator>susekar</dc:creator>
      <dc:date>2026-02-11T14:15:42Z</dc:date>
    </item>
  </channel>
</rss>

