The MSPro Boomi Collection
About
Boomi Console
Boomi Console
  • Boomi Console
    • What is ...
  • Installation & Setup
    • Download & Install
    • Setup a Workspace
    • Connect your Workspace
    • Test your Workspace
  • Commands
    • COMP - Components
      • GET
      • DOC
    • PACK - Packaged Components
      • PACK GET
      • PACK DOC
    • DEPLOY - Deployments
      • GET - Deployments and Packages
      • EXEC - Deploy components
        • Deployment from Repos
        • Promotion to Env
      • DELETE - Undeploy Components
    • WORKSPACE CONNECT
    • ACCOUNT INFO
    • Arguments
      • Common Arguments
        • The Set Argument in Detail
        • Query Filter
          • Start date or time span
        • Arguments in a file
        • Allow Multi
        • Component Resolution
      • COMP Arguments
        • COMP GET Arguments
        • COMP DOC Arguments
      • PACK Arguments
      • DEPLOY Arguments
        • DEPLOY GET Arguments
        • DEPLOY EXEC Arguments
        • DEPLOY DELETE Arguments
  • Use-Cases
    • Analyze deployed components
    • Components in a Folder
    • Deploy Components
    • Reveal a Process
    • Reveal an API Component
    • Deployed Components Overview
    • Deployment Task Document
    • Create a cSet.jsonc file
  • Library
    • Component Set
      • The Components Set JsonC file
        • Create a package file
      • Set File resolution
    • The Report Engine
      • Render DataSets
        • DataSet Base
        • Component Metadata DataSet
          • Component Metadata Header
          • Component Metadata
          • CompDataSet With Counts
        • Deployed Packages DataSet
        • Package Content DataSet
        • Map Markdown Dataset
      • Components
        • Deployable Components
        • Orphaned Components
    • The Workspace
      • Manage your workspace
      • Components Set Workspace
      • Workspace folders
      • The project database
    • Configuration files
      • Application Settings
      • Workspace configuration file
      • boomiConsole.user.json
    • How to...
      • Use Excel to view CSV files
      • Local metadata and caching
      • Getting help
      • Environments
      • How to get a Component's Id
    • Referenced Pages
      • Lists
      • Documentation Snapshots
  • Download and Release History
  • Help Text
    • Documentation Links
    • Target Path Resolution
    • GitHub Emojis
    • Packaged Component and Versions
    • Components and Versions
    • Component Hierarchy
    • Referenced Components
Powered by GitBook
On this page
  • CreateProcessPropertiesCsv
  • DocRoot
  1. Library
  2. Configuration files

Application Settings

Control the application default behaviour

Last updated 3 months ago

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

{
  "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:

DocRoot

Specify a path where all documentation is written to, by default, unless it is overruled by a command-line argument. Target Path Resolution.

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

@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