---
title: "ScriptBuilder Settings"
slug: "scriptbuilder-settings"
updated: 2026-10-07T11:33:53Z
published: 2026-10-07T11:33:53Z
canonical: "success.panaya.com/scriptbuilder-settings"
---
> ## Documentation Index
> Fetch the complete documentation index at: https://success.panaya.com/llms.txt
> Use this file to discover all available pages before exploring further.
# ScriptBuilder Settings
To define the ScriptBuilder settings, open ScriptBuilder from any script and click the menu button > Settings.
### General
#### Show ScriptBuilder always on top
Select Yes if you wish the ScriptBuilder to always stay on top of any other window in your operating system.
If you run ScriptBuilder in a multi-screen environment, it will start on the screen designated as the "main display" in your display settings.
#### Check for Updates
When a new ScriptBuilder version is available, you will be prompted with an option to install the new updates. Operating system administrator permissions are required to complete the setup.
To check for new ScriptBuilder updates, click the **menu** button and select **About**. Then click on **Check for new updates**.
#### Bypass Proxy Settings
In order for ScriptBuilder to work properly, some setup is required that includes whitelisting specific domains (see [Whitelisting Panaya Domains](https://success.panaya.com/docs/whitelisting-panaya-domains)) etc.
In some cases, there are additional processes on the machine that could block the traffic and prevent the connection (e.g. Proxy, see [Test Automation Proxy Settings](https://success.panaya.com/docs/test-automation-proxy-settings), Anti-virus and others).
By default, ScriptBuilder will consider the system’s Proxy settings when trying to connect. However, some organizations might set up the Proxy so that it’s only required for some software, but not for ScriptBuilder. In that case the user can “ignore” the system’s Proxy settings and connect directly to the internet by setting Bypass Proxy Settings to Yes. This will only work as long as the user can access the internet and is not blocked by any other way.
#### Use Chrome for Testing
Chrome updates can occasionally cause temporary compatibility issues that prevent ScriptBuilder from recording or playing scripts. Chrome for Testing is a controlled Chrome version that is less affected by unexpected browser changes.
Panaya Support may recommend enabling this option as a temporary workaround while compatibility with the latest Chrome version is restored.
> [!CAUTION]
> Important!
>
> Enable this option only when instructed by Panaya Support.
#### Install extension via BiDi (Chrome and Edge)
These settings control an alternative method for installing the Panaya browser extension in Google Chrome or Microsoft Edge. They are intended to help Panaya Support and Engineering troubleshoot extension installation or browser communication issues.
> [!CAUTION]
> Important!
>
> Do not change these settings unless instructed by Panaya Support.
###
### Default Settings & Script Properties
The **Default settings** section lets you define the default script settings for all new scripts created.
To define these settings for a specific script, without affecting newly created scripts, use the **Script Properties** section. Use the Script properties to override the default ScriptBuilder settings for specific scripts. 
> [!WARNING]
> Important!
>
> Component script settings are independent of the test’s script settings in which the component is nested. Changes made to the test’s script properties do not affect the component.
#### Date format
This date format setting will define how scriptBuilder inputs dates selected in date pickers into your recorded script. Selecting a date format that matches your AUT date format is recommended.
#### Time format
The time format setting determines how scriptBuilder interprets timestamps. Selecting a time format that matches your AUT time format is recommended.
#### Timeout (min)
The timeout setting defines the maximum time a script should run on an agent. If the time exceeds the limit, the agent will stop the run and mark it as failed.
#### Wait for execution
The Wait for execution of recorded instructions options allow centralized timeout control, addressing performance variability across environments, including cases where AUT servers affect execution speed.
The script settings support overriding or extending the “Wait for execution” timeout defined in the instruction timing.
ScriptBuilder provides a clear indication when the override or extend logic is applied per instruction. 
#### Supported applications
For supported applications, you can select from three options: Web Browser, SAP GUI, and Web Browser + SAP GUI. The Script Settings option allows you to override the default settings for a specific script.
#### AI playback self-healing
ScriptBuilder is equipped with a powerful self-healing mechanism. When locators fail to properly identify the target element, our smart engine can use AI for the instruction description as a fallback method, allowing it to intelligently locate the element when locators fail.
You can turn AI playback self-healing on or off for recording, playback, or both.
You can also set this option on or off [for each instruction](/v1/docs/ai-playback-self-healing#ai-selfhealing-configuration-at-instruction-level) separately.
[Learn more about AI playback self-healing](/v1/docs/ai-playback-self-healing)
#### Executing browser
Users can explicitly select the browser used for test runs. You can choose between the **operating system (OS) default browser**, **Google Chrome**, or **Microsoft Edge**.
Browser selection can be configured in the script settings but can be overridden by execution schedule settings and on-demand execution selection.
#### **SAP Connection Settings**
Use this to select the type of SAP GUI connection and determine how ScriptBuilder will connect to your SAP GUI.
[Learn more](/v1/docs/sap-connection-settings-in-scriptbuilder)
---
##
## Related
- [SAP GUI Connection Settings in ScriptBuilder](/sap-connection-settings-in-scriptbuilder.md)