# Application Settings

There are two files which will be merged on start-up, where the workspace settings (if they exist) override the default settings from the application's binary directory:

* `{AppBinDir}\appsettings.json`
* `{WorkspaceDir}\appsettings.json`

```json
{
  "AppSettings": {
    "TemplateMaxDataSetCount": 0,
    "CreateProcessPropertiesCsv" : false,
    "RenderVersioned" : false,
    "DocRoot" : "path"
  }
}
```

### CreateProcessPropertiesCsv

If set to *true* a `prop.{ProcessComponentId~version}.csv` will be created for each process. This file contains a list of all used properties with this process.

This is extremely useful when you want to see which property is used where:

<figure><img src="/files/Kgs2Mne9QQLifeyr6VdT" alt=""><figcaption></figcaption></figure>

### DocRoot

Specify a path where all documentation is written to, by default, unless it is overruled by a command-line argument. [Target Path Resolution](/boomi-console/help-text/target-path-resolution.md).

{% hint style="success" %}
Personally, I prefer to use `{AccountName}` as the documentation output. For example. `<workspace>\boomi_markusschmidt-xxxxx`.

On the other end, I put this directory under version control, for example:

`https://gitlab.com/boomi123/boomi_markusschmidt-xxxxx`

After running COMP DOC, I add, commit and push all files: `save.bat`

```batch
@echo off
set GIT_DIR=boomi_markusschmidt-xxxxx
call git --git-dir=%GIT_DIR%/.git add .
call git --git-dir=%GIT_DIR%/.git commit -m "COMP DOC"
call git --git-dir=%GIT_DIR%/.git push
```

{% endhint %}


---

# 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://boomi.markusschmidt.pro/boomi-console/library/configuration-files/application-settings.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.