> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/customize-cases-and-issues/customize-issue-fields-and-layouts/issue-layouts/add-a-custom-widget-to-an-issue-layout.md).

# Add a custom widget to an issue layout

Add custom or system widgets to Cortex XSIAM issue layouts with dynamic-section scripts and layout rules.

You can add a custom or system widget to a custom issue layout by uploading an auto script and using it in a **General Purpose Dynamic Section** in your layout.

The following example shows how to add an Indicator Widget Bar. This custom widget script shows the severity of indicators in an issue, as a bar chart.

1. Add the Indicator Widget Bar script to Cortex XSIAM.

   1. Go to **Investigation & Response** → **Automation** → **Scripts** and upload the following script:

   ```
   commonfields:
     id: ee3b9604-324b-4ab5-8164-15ddf6e428ab
     version: 49
   name: IndicatorWidgetBar
   script: |-
     # Constants
     HIGH = 3
     SUSPICIOUS = 2
     LOW = 1
     NONE = 0

     indicators = []
     scores = {HIGH: 0, SUSPICIOUS: 0, LOW: 0, NONE: 0}
     incident_id = demisto.incidents()[0].get('id')

     foundIndicators = demisto.executeCommand("findIndicators", {"query":'investigationIDs:{}'.format(incident_id), 'size':999999})[0]['Contents']

     for indicator in foundIndicators:
         scores[indicator['score']] += 1

     data = {
       "Type": 17,
       "ContentsFormat": "bar",
       "Contents": {
         "stats": [
           {
             "data": [
               scores[HIGH]
             ],
             "groups": None,
             "name": "high",
             "label": "incident.severity.high",
             "color": "rgb(255, 23, 68)"
           },
           {
             "data": [
               scores[SUSPICIOUS]
             ],
             "groups": None,
             "name": "medium",
             "label": "incident.severity.medium",
             "color": "rgb(255, 144, 0)"
           },
           {
             "data": [
               scores[LOW]
             ],
             "groups": None,
             "name": "low",
             "label": "incident.severity.low",
             "color": "rgb(0, 205, 51)"
           },
           {
             "data": [
               scores[NONE]
             ],
             "groups": None,
             "name": "unknown",
             "label": "incident.severity.unknown",
             "color": "rgb(197, 197, 197)"
           }
         ],
         "params": {
             "layout": "horizontal"
         }
       }
     }

     demisto.results(data)
   type: python
   tags:
   - dynamic-section
   enabled: true
   scripttarget: 0
   subtype: python3
   runonce: false
   dockerimage: demisto/python3:3.7.3.286
   runas: DBotWeakRole
   				
   ```

   1. Click Save
2. Go to Settings → Configurations → Object Setup → Issues → Layout Rules → **New Rule**.
3. Enter a rule name, select the layout to use if the rule is met, and provide a description.
4. Search for issues that match the criteria you want to use for the layout rule. For example, you can search for issues from a specific issue source.
5. Click **Create**.
6. Repeat as needed to create multiple rules.
7. Click **Save**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/customize-cases-and-issues/customize-issue-fields-and-layouts/issue-layouts/add-a-custom-widget-to-an-issue-layout.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.