> 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/application-security/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/branch-periodic-scans/references/reference-a-inventory-columns.md).

# Reference A: Inventory columns

The Branch Periodic Scans inventory displays the following columns by default. Each column supports sorting. Filterable columns support text-based and enum-based filtering according to the data type. You can retrieve matching response fields through the [Scan Management API](/cortex-cloud-api/aspm-cicd-and-application-security/scan-management.md).

| Column                         | Field        | Description                                                                                                                        |
| ------------------------------ | ------------ | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Repository**                 | `repoName`   | The name of the scanned repository, displayed with the VCS provider icon                                                           |
| **Scanned Branch**             | `branchName` | The branch analyzed during the scan                                                                                                |
| **Scan Date**                  | `scanDate`   | The timestamp of the last scan execution                                                                                           |
| **Scan Health**                | `scanHealth` | The execution health of the scan                                                                                                   |
| **Business Application Names** |              | The business applications associated with the scanned repository. Enable this column to rank scan failures by business criticality |

The following columns are hidden by default. Enable additional columns from the column settings icon in the inventory toolbar.

| Column            | Field              | Description                                            |
| ----------------- | ------------------ | ------------------------------------------------------ |
| **Organization**  | `organizationName` | The VCS organization or group that owns the repository |
| **Scan ID**       | `scanId`           | The unique identifier of the scan                      |
| **Repository ID** | `repositoryId`     | The unique identifier of the repository                |
| **Integration**   | `integrationId`    | The identifier of the VCS integration                  |
| **Scan Category** |                    | Filters results by Code, LLM, or All                   |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/application-security/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/branch-periodic-scans/references/reference-a-inventory-columns.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.