> 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-developer-guide/cortex-xsiam-development-guide/alerts.md). # Issues Create a content pack for Cortex XSIAM with custom content for issues. When you create a content pack for Cortex XSIAM, you can include custom issue layouts, fields, and rules, as well as classifiers and mappers. Develop these items in the UI. * Issue fields - Issue fields support mapping, correlation rules, custom issue layouts, and display in the Issues table. * Issue layouts - Custom issue layouts let you choose fields and buttons for issues that meet specific rules. You can include custom and out-of-the-box issue fields. * Issue layout rules - Issue layouts are applied according to layout rules. You can assign a custom layout based on the issue source, including issues from your integration. * Classifiers - Classification determines the issue type created for events from a specific integration. Create and define the classifier in the integration. * Mappers - Map fields from your third-party integration to issue fields. After these items have been created and finalized, we can add them to the content pack by downloading them using `demisto-sdk download -i "Resource Name" -o Packs/MyPack`. The SDK will put the content item in the correct subfolder per the type of resource it is. --- # 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-developer-guide/cortex-xsiam-development-guide/alerts.md?ask=&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.