> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-connect/reference/reference/portal/design-items/common-portlet-configuration/general.md).

# General

## General

* **Name:** the name of the portlet

{% hint style="info" %}
**Dynamic Titles:** Dynamic titles can be used in portlet names to provide more details about the content being presented. For this functionality to work, the portlet must have access to data from other portlets as a parameter. To achieve this, the portlet should listen to the data provided by other portlets.

To add a dynamic value to the title, include the parameter in the portlet's name using curly brackets `{}`. For example, the title "Product Info: {ProductId}" would display the selected product ID in the title, assuming the parameter name is `ProductId`.
{% endhint %}

* **Header Visibility:** Determines the behavior of the portlet and container headers.
  * **Visible:** The header will always be shown.
  * **Visible on Hover:** The header will be visible when the user hovers over the header area. The header can be accessed by hovering over the small handle located in the upper right corner for portlets and the upper left corner for containers.
  * **Hidden:** The header is always hidden. If the header is hidden, users cannot access the action buttons (e.g., Clear User Settings, Refresh, Expand, etc.). When in edit mode, the "Hidden" setting behaves the same as "Visible on Hover," meaning the header will become visible when the user hovers over the header area.
* **Header style:** Expand Header style to customize the appearance of a portlet or container header.
  * **Size:** Select Small, Medium, Large, or Extra large. The size determines the title’s font size and the spacing above and below it.
  * **Bold:** Enable this option to display the title in bold.
  * **Background:** Set the header’s background colour. Clear the colour to use the theme default.
  * **Title text:** Set the title’s text colour. Clear the colour to use the theme default.
* **Stacked container tabs:** For stacked containers, the header and tabs are configured separately. Tab styling supports Size and Bold, with the same settings applied to all tabs.
* **Auto-Refresh:** Enables the portlet to refresh its data every SS seconds. If there are unsaved changes in the columns, the table will not refresh until those changes have been saved or canceled.

{% hint style="warning" %}
**Auto-Refresh should be used with caution**: Portlets that rely on heavy queries in the data source and are set to refresh too frequently can cause performance issues. Designers should carefully consider the intended usage before configuring the refresh interval.
{% endhint %}


---

# 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.novacura.com/flow-connect/reference/reference/portal/design-items/common-portlet-configuration/general.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.
