---
title: "How to use the Advanced Configuration"
canonical: "https://support.appfire.com/space/PSJ/15482103/How%20to%20use%20the%20Advanced%20Configuration"
format: markdown
---
> Macro (aura-html)
The Advanced configuration interface consists of three tabs. Each tab represents a step in the field configuration process.
- **General**: Basic field settings and behavior options.
- **Column List**: Column configuration and display settings.
- **Scripts**: Custom SQL/SIL scripts for field operations.
> ℹ️ The available settings differ based on the type of field you're configuring. Readonly fields (Simple Select, Multi Select, Autocomplete) have simplified settings compared to editable fields, as some configuration options like security actions and auto search only apply to editable fields.
Let's walk through each step of the process.
---
## Step 1: Configure the General tab settings
The *General* tab contains the core field settings. The available options depend on the **Display Type** you select for your field.
| **Configuration settings for readonly fields** | **Configuration settings for editable fields** |
| --- | --- |
| Readonly fields support three display type options:
- **Simple select**
- **Multi select**
- **Autocomplete**
 | Editable fields use the **Generic** display type exclusively.
 |
The following table shows all available settings in the *General* tab. Some settings are shared between field types, while others are specific to editable fields only:
| **Setting** | **Readonly fields** | **Editable (generic) fields** | **Control type** | **Description** |
| --- | --- | --- | --- | --- |
| **SQL Database Source** | :check_mark: | :check_mark: | Dropdown menu | Determines which data source the field uses for retrieving data. Data sources must be preconfigured before they appear as selectable options.
> ℹ️ For configuration instructions, see the [Configuring data sources](https://appfire.atlassian.net/wiki/spaces/PSJ/pages/15483997) guide. You can also manually enter any JNDI identifier that has been internally configured in Jira. |
| **Auto Search** | :cross_mark: | :check_mark: | Toggle switch | Automatically triggers search when users open the *Search* dialog, using values already present in the field. |
| **Hide Column Labels** | :cross_mark: | :check_mark: | Toggle switch | This toggle controls the visibility of column labels when the field is displayed. Enable it to hide labels in the field rendering.
 |
| **Use Auto-Bind** | :check_mark: | :check_mark: | Toggle switch | Automatically recalculates field values when dependent fields change. If your field depends on other fields, enabling this setting intercepts changes in those fields and triggers value recalculation.
> ✅ For advanced control, consider using the [Live Fields](https://appfire.atlassian.net/wiki/spaces/PSJ/pages/15488008) feature of Power Scripts instead. |
| **Refresh Type** | :check_mark: | :check_mark: | Dropdown menu | Controls how and when the field refreshes data from the source database. Choose an option based on how frequently your source data changes:
- **NEVER**: Field data never updates, even if the source database data changes.
- **ALWAYS**: Field data updates every time it's viewed by querying the database. Use only for frequently changing data, as this can impact system performance.
- **EXPIRES**: Field data updates after a specified time interval (for example, "1w" for weekly, "1d" for daily). Use standard Jira time interval format. This option provides better performance than **ALWAYS** while keeping data reasonably current. |
| **Security Type** | :cross_mark: | :check_mark: | Dropdown menu + Toggle switch | Combines action capabilities with permission settings to control what users can do with the field and database. You configure both which actions are available and who can perform them.
**Security type (permissions):**
- **ALLOW ALL**: Users can perform all database actions.
- **DENY ALL**: No users can perform any database actions.
- **FIXED**: Configure permissions for each action independently.
- **DYNAMIC**: Use custom scripts to determine permissions based on issue context or Jira environment variables. See the [How to write Security scripts](https://appfire.atlassian.net/wiki/spaces/PSJ/pages/15482042) page for details.
**Actions:**
- **Allow Set**: Users can search and select values. Triggers the `SEARCH` and `SET` scripts. If enabled, a dedicated **Search** icon appears in the field's Actions panel.
- **Allow Insert**: Users can add new values to the connected database table. Triggers the `INSERT` script when completed. If enabled, a dedicated **Insert** icon appears in the field’s Actions panel.
- **Allow Update**: Users can modify existing values in both Jira and the connected database table. Triggers the `UPDATE` script when completed. If enabled, a dedicated **Update** icon appears in the field’s Actions panel.
- **Allow Delete**: Users can remove data from both Jira and the connected database table. Triggers the `DELETE` script when completed. If enabled, a dedicated **Delete** icon appears in the field’s Actions panel.
 |
---
## Step 2: Configure the Column List
The *Column List* tab lets you configure settings for individual columns that compose the Advanced Row Field.
> ℹ️ The field's **Display Type** (configured in the General tab) significantly influences what needs to be configured in the *Column Lis*t tab.
| **Configuration settings for readonly fields** | **Configuration settings for editable fields** |
| --- | --- |
| For fields **Display Type** set to** Simple select**, **Multi select**, or **Autocomplete**, only two columns should be configured:
- One field acts as the primary key;
- The other field contains the data displayed by the field. | For fields with** Display Type** set to** Generic**, multiple columns can be configured to provide full functionality.
 |
The following table shows all available column settings:
| **Setting** | **Description** |
| --- | --- |
| **Physical Name** | Specifies the exact column name as it exists in the database table. |
| **Label** | Defines the display name for the column in Jira's interface. This setting only applies to Generic Advanced Row Fields, as readonly fields don't display column labels. Label visibility is controlled by the **Hide Column Labels** setting in the *General* tab. |
| **Type** | Specifies the column's data type for validation and indexing purposes. Available options include `BOOLEAN`, `NUMBER`, `REAL`, `STRING`, `DATE`, `DATETIME`, and `SEQUENCE` (for auto-generated primary keys). The selected type determines which constraints are available and enables appropriate JQL search operators.
> ℹ️ See the [How to use column constraints](https://appfire.atlassian.net/wiki/spaces/PSJ/pages/15482044) page for details. |
| **Default Value** | Sets the initial value that appears in the Insert form's input field for this column. |
| **PK** | Identifies this column as the primary key in the connected database table. |
| **Searchable** | When set to **Yes**, this function makes the column available in the *Search* dialog, enabling its value to be used in `SEARCH` scripts.
You can also streamline single-column searching by designating one column as **Autocomplete**. Autocomplete columns have additional configuration options (like minimum character requirements) accessible through the adjacent **Settings** icon.
As illustrated in this screenshot, when any column is set to **Autocomplete**, all other columns' Searchable settings are automatically reset to **No**.
 |
| **Required** | Makes the column mandatory for `INSERT`/`UPDATE` operations. Required columns display an asterisk (*) next to their label, and users must fill the corresponding input field before submitting forms. |
| **Constraints** | Defines validation rules that input data must satisfy before values can be saved. These conditions ensure data integrity and enforce business rules. |
---
## Step 3: Configure the field’s scripts
On the *Scripts* tab, you configure field scripts that execute for each supported operation. Available operations vary depending on your field's display type.
| **Configuration settings for readonly fields** | **Configuration settings for editable fields** |
| --- | --- |
| Support a limited set of operations: `DEFAULT`, `GET`, and `SEARCH`.
> ℹ️ See the [How to configure scripts for readonly fields](https://appfire.atlassian.net/wiki/spaces/PSJ/pages/542769264) page for detailed guidance. | Support the complete operation set: `DEFAULT`, `GET`, `SET`, `INSERT`, `UPDATE`, `DELETE`, `SEARCH`, and `SEQ`.
> ℹ️ See the [How to configure scripts for editable fields](https://appfire.atlassian.net/wiki/x/DgBeI) page for detailed guidance. |
The following table explains the key interface elements and behaviors when working with scripts in the *Scripts* tab:
| | | |
| --- | --- | --- |
|  | The Scripts configuration interface uses SQL syntax by default, shown by a small indicator icon next to each operation. |  |
|  | You can switch to SIL scripts by right-clicking any operation.
> ℹ️ Mixing script types is supported. SIL scripts include built-in syntax validation, while SQL scripts require manual verification for your database type. |
|  | Color-coded operation labels show configuration status (green for configured, red for missing). You only need to configure the operations you plan to use. |
|  | Selecting any operation opens a Details panel with additional configuration options. |  |
|  | Each script can use additional parameters from Jira screen fields or issue fields (both standard and custom).
> ℹ️ See [How to use script parameters](https://appfire.atlassian.net/wiki/spaces/PSJ/pages/15487441) for detailed guidance. |