> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/9.3-analytics/pentaho-analyzer-cp/creating-analyzer-reports/visualizations-for-analyzer.md).

# Visualizations for Analyzer

After you have created an analysis report, you will most likely want to make the report more visually pleasing and meaningful for your audience. Analyzer has quite a few built-in visualizations that give you an effective means for presenting your data in a way that people can intuitively understand. We also give you many different ways to customize your visualizations.

Both the **Layout** and **Property** panels in the Analyzer workspace dynamically change based on the visualization that you currently have selected. The **Layout** panel shows you what data is needed for that particular visualization, and the **Property** panel lets you add or change options such as data labels, color patterns, or bullet styles.

The optional properties for each visualization type are listed in each section. You can use any or all of these properties for each visualization to make your report more intuitive for your audience. The [Chart Options](https://docs.pentaho.com/pba/9.3-analytics/pentaho-analyzer-cp/creating-analyzer-reports/chart-options-for-analyzer-reports-cp.md) dialog box contains more ways to customize your reports.


---

# 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://docs.pentaho.com/pba/9.3-analytics/pentaho-analyzer-cp/creating-analyzer-reports/visualizations-for-analyzer.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.
