<?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: Limitations Observed with XQL Custom Widgets and Issue Visibility in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/limitations-observed-with-xql-custom-widgets-and-issue/m-p/1244987#M8960</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/831392957"&gt;@Jai_Prakas&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;H3&gt;1. Auto Refresh Limitation&lt;/H3&gt;
&lt;P&gt;The behavior you observed is a known&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;design limitation&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;of the product.&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Expected Behavior:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Custom XQL widgets do not currently support automatic refresh intervals and typically require a manual click of the "Update Now" button to reflect the most recent data.&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Workaround:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Currently, there is no configuration to enable real-time auto-refresh for custom widgets. Users must manually refresh the widget or the dashboard.&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Roadmap:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;There is an active enhancement request being tracked under&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;CRTX-37773&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;to provide customizable refresh intervals for Custom XQL Widgets.&lt;/P&gt;
&lt;H3&gt;2. Drill-Down Limitation in XQL Widgets&lt;/H3&gt;
&lt;P&gt;Custom widgets do not automatically inherit the dynamic, context-aware drill-down capabilities found in predefined system widgets.&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Expected Behavior:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;While predefined widgets use hard-coded server-side logic to redirect to specific filtered views, custom XQL widgets are limited to the URL configured in the drill-down settings.&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Partial Workaround:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;You can construct a custom URL that uses dynamic parameters to capture values from the widget's axis. For example, using&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;$x_axis.value&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;$y_axis.value&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;in your URL string can allow the platform to replace those placeholders with the actual clicked value.&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Syntax Example:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;https://[TENANT_URL]/endpoints/agents?platform=AGENT_OS_$x_axis.value&lt;/CODE&gt;&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Constraint:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;This only works if the destination page has a valid URL parameter that accepts the value being passed. If the specific field (like a granular "Issue" attribute) is not exposed as a filterable column on the target page, the navigation will fail or just refresh the current page.&lt;/P&gt;
&lt;H3&gt;3. No Predefined Widget for Issues&lt;/H3&gt;
&lt;P&gt;The absence of a predefined widget for "Issues" is consistent with current product findings where specific visualizations for certain datasets are not available out-of-the-box.&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Status:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Predefined widgets are typically "hard-coded" for specific use cases (like Cases or Incidents) and cannot be easily modified or cloned into different datasets.&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Workaround:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;The recommended approach is to continue building custom XQL widgets using the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;incidents&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or relevant issue-based datasets to achieve the desired visibility.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Recommendation:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;For features like the Issues widget or enhanced dynamic drill-down behavior that are not currently supported, it is advised to coordinate with your&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Account Team or Sales Engineer&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;to submit or upvote a formal&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Feature Request (FR)&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&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;"mark this as a Solution".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Happy New year!!&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;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 06 Jan 2026 20:05:09 GMT</pubDate>
    <dc:creator>susekar</dc:creator>
    <dc:date>2026-01-06T20:05:09Z</dc:date>
    <item>
      <title>Limitations Observed with XQL Custom Widgets and Issue Visibility</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/limitations-observed-with-xql-custom-widgets-and-issue/m-p/1244801#M8943</link>
      <description>&lt;P class="isSelectedEnd"&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;&lt;SPAN&gt;We are facing multiple limitations while creating &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;custom widgets using XQL&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;, which are impacting our dashboard visibility and operational efficiency. The details are outlined below:&lt;/SPAN&gt;&lt;/P&gt;
&lt;OL start="1" data-spread="true"&gt;
&lt;LI&gt;
&lt;P class="isSelectedEnd"&gt;&lt;STRONG&gt;&lt;SPAN&gt;Auto Refresh Limitation&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;When creating a custom widget using XQL, there is no option to configure &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;automatic refresh intervals&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;. Currently, the widget refreshes only once every &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;24 hours&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;For our environment, we require auto-refresh options such as &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;1 minute, 5 minutes, 10 minutes, or 1 hour&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; to maintain near real-time visibility.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P class="isSelectedEnd"&gt;&lt;STRONG&gt;&lt;SPAN&gt;Drill-Down Limitation in XQL Widgets&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;While configuring drill-down for a custom XQL widget, we are able to add &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;only one static URL&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;This limits dynamic drill-down behavior based on widget values.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;&lt;STRONG&gt;&lt;SPAN&gt;Example:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;If the widget shows &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;20 total issues&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; categorized as:&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL data-spread="false"&gt;
&lt;LI&gt;
&lt;P class="isSelectedEnd"&gt;&lt;SPAN&gt;5 Critical&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P class="isSelectedEnd"&gt;&lt;SPAN&gt;10 Medium&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P class="isSelectedEnd"&gt;&lt;SPAN&gt;3 High&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P class="isSelectedEnd"&gt;&lt;SPAN&gt;2 Low&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P class="isSelectedEnd"&gt;&lt;SPAN&gt;Clicking on &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;“High”&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; should ideally open a filtered view showing &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;only High-severity issues&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;. However, the drill-down does not redirect to the corresponding issue list based on severity, making the widget less actionable.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P class="isSelectedEnd"&gt;&lt;STRONG&gt;&lt;SPAN&gt;No Predefined Widget for Issues&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Currently, there is &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;no predefined widget available for Issues&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;, which limits clear and direct visibility of issues on the dashboard. This is a significant gap, especially when compared to the availability of predefined widgets for Cases.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P class="isSelectedEnd"&gt;&lt;SPAN&gt;Due to the above constraints, it becomes difficult to achieve &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;real-time monitoring and effective issue-level visibility&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; through the dashboard.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="isSelectedEnd"&gt;&lt;SPAN&gt;Kindly clarify:&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL data-spread="false"&gt;
&lt;LI&gt;
&lt;P class="isSelectedEnd"&gt;&lt;SPAN&gt;Whether these limitations are expected behavior&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P class="isSelectedEnd"&gt;&lt;SPAN&gt;If there is any workaround available&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P class="isSelectedEnd"&gt;&lt;SPAN&gt;Or if there is a product roadmap to address these gaps&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN&gt;Thanks &amp;amp; regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;SPAN&gt;Jai Prakash&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;&lt;LI-PRODUCT title="Cortex XDR" id="Cortex_XDR"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jan 2026 15:01:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/limitations-observed-with-xql-custom-widgets-and-issue/m-p/1244801#M8943</guid>
      <dc:creator>Jai_Prakas</dc:creator>
      <dc:date>2026-01-03T15:01:38Z</dc:date>
    </item>
    <item>
      <title>Re: Limitations Observed with XQL Custom Widgets and Issue Visibility</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/limitations-observed-with-xql-custom-widgets-and-issue/m-p/1244987#M8960</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/831392957"&gt;@Jai_Prakas&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;H3&gt;1. Auto Refresh Limitation&lt;/H3&gt;
&lt;P&gt;The behavior you observed is a known&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;design limitation&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;of the product.&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Expected Behavior:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Custom XQL widgets do not currently support automatic refresh intervals and typically require a manual click of the "Update Now" button to reflect the most recent data.&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Workaround:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Currently, there is no configuration to enable real-time auto-refresh for custom widgets. Users must manually refresh the widget or the dashboard.&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Roadmap:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;There is an active enhancement request being tracked under&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;CRTX-37773&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;to provide customizable refresh intervals for Custom XQL Widgets.&lt;/P&gt;
&lt;H3&gt;2. Drill-Down Limitation in XQL Widgets&lt;/H3&gt;
&lt;P&gt;Custom widgets do not automatically inherit the dynamic, context-aware drill-down capabilities found in predefined system widgets.&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Expected Behavior:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;While predefined widgets use hard-coded server-side logic to redirect to specific filtered views, custom XQL widgets are limited to the URL configured in the drill-down settings.&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Partial Workaround:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;You can construct a custom URL that uses dynamic parameters to capture values from the widget's axis. For example, using&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;$x_axis.value&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;$y_axis.value&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;in your URL string can allow the platform to replace those placeholders with the actual clicked value.&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Syntax Example:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;https://[TENANT_URL]/endpoints/agents?platform=AGENT_OS_$x_axis.value&lt;/CODE&gt;&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Constraint:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;This only works if the destination page has a valid URL parameter that accepts the value being passed. If the specific field (like a granular "Issue" attribute) is not exposed as a filterable column on the target page, the navigation will fail or just refresh the current page.&lt;/P&gt;
&lt;H3&gt;3. No Predefined Widget for Issues&lt;/H3&gt;
&lt;P&gt;The absence of a predefined widget for "Issues" is consistent with current product findings where specific visualizations for certain datasets are not available out-of-the-box.&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Status:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Predefined widgets are typically "hard-coded" for specific use cases (like Cases or Incidents) and cannot be easily modified or cloned into different datasets.&lt;BR /&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Workaround:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;The recommended approach is to continue building custom XQL widgets using the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;incidents&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or relevant issue-based datasets to achieve the desired visibility.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Recommendation:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;For features like the Issues widget or enhanced dynamic drill-down behavior that are not currently supported, it is advised to coordinate with your&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Account Team or Sales Engineer&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;to submit or upvote a formal&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Feature Request (FR)&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&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;"mark this as a Solution".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Happy New year!!&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;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jan 2026 20:05:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/limitations-observed-with-xql-custom-widgets-and-issue/m-p/1244987#M8960</guid>
      <dc:creator>susekar</dc:creator>
      <dc:date>2026-01-06T20:05:09Z</dc:date>
    </item>
  </channel>
</rss>

