# All Configuration

## Configuration Field/Keys

<table data-full-width="false"><thead><tr><th width="285">Key</th><th>Description</th></tr></thead><tbody><tr><td>showUrl</td><td><strong>boolean</strong> Determines if the URL will be displayed to the user. Defaults to <code>false</code>.</td></tr><tr><td>showTitle</td><td><strong>boolean</strong> Determines if the webpage title is displayed to the user. Defaults to <code>false</code>.</td></tr><tr><td>allowCookiePreview</td><td><strong>boolean</strong> Determines if user can view the cookies for the current URL. This is used for development purposes. Defaults to <code>false</code>.</td></tr><tr><td>fixOrientation</td><td><strong>boolean</strong> Determines if the view is fixed to portrait. Defaults to <code>false</code>.</td></tr><tr><td>allowUrlEdit</td><td><strong>boolean</strong> Determines if the user is allowed to edit the URL. Defaults to <code>false</code>.</td></tr><tr><td>allowPullToRefresh</td><td><strong>boolean</strong> Indicates if the browser page can be pulled down to reload the current page.  Default is <code>false</code>.</td></tr><tr><td>defaultHomepage</td><td><strong>string</strong> URL of the website to be visited when the browser application is clicked. Defaults to a blank URL.</td></tr><tr><td>enablePinchToZoom</td><td><strong>boolean</strong> Determines if the user is allowed to pinch to zoom within the webpage. Defaults to <code>false</code>.</td></tr><tr><td>allowInsecureSites</td><td><strong>boolean</strong> Determines if the user is allowed to visit insecure websites. Defaults to <code>false</code>.</td></tr><tr><td>allowCameraAccess</td><td><strong>boolean</strong> Determines if the website can access the camera. Defaults to <code>false</code>.</td></tr><tr><td>allowAudioCapture</td><td><strong>boolean</strong> Determines if the website can access the microphone. Defaults to <code>false</code>.</td></tr><tr><td>allowPrinterAccess</td><td><strong>boolean</strong> Determines if the website can access the printers. Defaults to <code>false</code>.</td></tr><tr><td>allowPopupWindows</td><td><strong>boolean</strong> Determines if the website can display pop-up windows over webpage content within the browser. Defaults to <code>false</code>.</td></tr><tr><td>logLevel</td><td><strong>string</strong> Determines the level of log to be logged in Support Agent. Valid values are <code>verbose</code>, <code>debug</code>, <code>info</code>, or <code>error</code>. If set, only the level of logs set and below will be logged. Defaults to <code>info</code>.</td></tr><tr><td>openInDesktopMode</td><td><strong>boolean</strong> If used in a <code>browserOverrides</code> object and set to <code>true</code>, the browser will open the website with a user agent to tell the browser to render it in desktop mode. Defaults to <code>false</code>.</td></tr><tr><td>allowThirdPartyCookies</td><td><strong>boolean</strong> Determines if the website can use/store third-party cookies. Defaults to <code>false</code>.</td></tr><tr><td>enableEmsApi</td><td><strong>boolean</strong> Enable the Launcher Provider, Keyboard, and Scanner APIs to be used from a webpage. Defaults to <code>false</code>.</td></tr><tr><td>userAgent</td><td><strong>string</strong> A replacement user agent string to send to the server; the server will process data from the application as if it was coming from a different web browser, as defined by the string. If not specified, will default to the device-provided user agent string. Can be overridden by the value in a shortcut's <code>browserOverrides</code>.</td></tr><tr><td>customScriptPath</td><td><strong>string</strong> The file location, using the file path on the device or an <a href="/pages/MJ0KAw0qT7KdUaqNlm4O">asset</a>, of a Javascript file applied to implement a custom behavior on the BlueFletch Browser.</td></tr><tr><td>customStylePath</td><td><strong>string</strong> The file location, using the file path on the device or an asset, of a CSS file applied to implement custom styles on the BlueFletch Browser.</td></tr><tr><td>createDataWedgeProfile</td><td><strong>boolean</strong> Determines whether or not a DataWedge profile will be automatically created for the BlueFletch Browser when the application is first launched. Defaults to <code>true</code> (profile is automatically created). Applicable to Zebra devices only.</td></tr><tr><td>disableBackButton</td><td><strong>boolean</strong> If <code>true</code>, the Android Back button will be disabled while a Browser web app is open. Default is <code>false</code>.</td></tr><tr><td>disableBackButtonMessage</td><td><strong>string</strong> If <code>disableBackButton</code> is <code>true</code>, a toast message will display the defined text string upon tapping Android Back button. Text defaults to "Back button has been disabled for this app".<br>To not display any toast for a particular web app while Back button is disabled, define this value with an empty string within the web app's <code>browserOverrides</code> object.</td></tr><tr><td>useWideViewPort</td><td><strong>boolean</strong> Sets whether the WebView should enable support for the "viewport" HTML meta tag or should use a wide viewport. Default is <code>true</code>.</td></tr><tr><td>scannerDisableProfile</td><td><strong>boolean</strong> When using the Javascript Scanner interface logic, the <code>Scanner.disable</code> and <code>Scanner.unregister</code> functions will disable the scanner hardware on Zebra devices. Set this flag to 'false' to ignore scan events and not disable the scanner hardware. Default is <code>true</code>, introduced in version 2.0.10</td></tr><tr><td>webauthnPaths</td><td><strong>string</strong> Comma-delimited list of hosts where the WebAuthn (FIDO2) interfaces will be enabled within the Browser.  If set and the current page matches the host, Browser will allow the use of FIDO2 with NFC security keys on that page.</td></tr><tr><td>clearCacheOnExit</td><td><strong>boolean</strong> If set to <code>true</code>, when the browser closes, will invoke logic to clear cache.  Default is <code>false</code>.  Introduced in version 2.3.4</td></tr><tr><td>clearCookiesOnExit</td><td><strong>boolean</strong> If set to <code>true</code>, when browser closes, will invoke logic to clear cookies.  Default is <code>false</code>.  Introduced in version 2.3.4</td></tr><tr><td>enableLauncherHid</td><td><strong>boolean</strong> If set to <code>true</code>, when Launcher is running and Browser is in the foreground, HID scanning (sending scanned data as keystrokes) is enabled. Default is <code>false</code>. Introduced in version 2.3.11.</td></tr><tr><td>intentAllowedPackages</td><td><strong>Array</strong> A list of packages that if present can be used to handle webpage Intents.</td></tr><tr><td>appLinkPaths</td><td><strong>string</strong> If an application uses https:// deep links to open a native application from the browser, specify the URL in this configuration field. Multiple URLs can be used separated by a comma. </td></tr></tbody></table>

#### Notes <a href="#notes" id="notes"></a>

* To completely hide the header bar (which consists of a toolbar and overflow menu) at the top of a Browser page, ensure that **none** of the following is `true` globally, or is set to `false` in a shortcut's `browserOverrides` :&#x20;
  * If `true`, these show the toolbar (webpage title or URL for viewing or editing):
    * `showUrl`
    * `showTitle`
    * `allowUrlEdit`
  * If `true`, these show the overflow (three-dot) menu:
    * `allowCookiePreview`
    * `allowPrinterAccess`
* If the `"defaultHomepage"` is not set, the browser will not launch when the user clicks on the browser application and an error will be displayed.

## Sample Browser Configuration&#x20;

```
"browser": {
    "showUrl": false,
    "showTitle": false,
    "allowCookiePreview": false,
    "fixOrientation": false,
    "allowUrlEdit": false,
    "defaultHomepage": "https://bluefletch.com",
    "enablePinchToZoom": false,
    "allowInsecureSites": false,
    "allowCameraAccess": false,
    "allowAudioCapture": false,
    "allowPrinterAccess": false,
    "enableEmsApi": false,
    "logLevel": "info",
    "createDataWedgeProfile": true,
    "disableBackButton": false   
},
"browserRestrictions": {
    "allowList" : [],
    "blockList" : []
}
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bluefletch.com/bluefletch-enterprise/product-guides/browser/technical-guide/all-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.