> For the complete documentation index, see [llms.txt](https://boomi.markusschmidt.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boomi.markusschmidt.pro/boomi-console/library/configuration-files/application-settings.md).

# 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 %}