> 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-report-designer/9.3-report-designer/style-properties-reference/object-styles.md).

# Object styles

**Object** styles control the appearance of shape elements.

| Property Name    | Data Type | Purpose                                                                                                        |
| ---------------- | --------- | -------------------------------------------------------------------------------------------------------------- |
| **fill**         | Boolean   | A flag indicating whether the given shape should be filled.                                                    |
| **fill-color**   | Selection | Defines alternative **fill-colors**. If undefined, the foreground color is used.                               |
| **draw-outline** | Boolean   | Defines whether the **shape-outline** should be drawn in the foreground color.                                 |
| **stroke**       | Selection | Defines the stroke (pen type and width) that should be used to render a shape.                                 |
| **anti-alias**   | Boolean   | Defines whether drawable content should be rendered with **anti-aliasing** enabled.                            |
| **aspect-ratio** | Boolean   | A flag indicating whether the scaling should preserve the aspect ratio.                                        |
| **scale**        | Boolean   | A flag indicating whether the content printed in the element should be scaled to fit the element's boundaries. |


---

# 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-report-designer/9.3-report-designer/style-properties-reference/object-styles.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.