Download and Release History

Boomi Console Release History

DOWNLOAD

• win-x64 releases are: unzip and run - on Windows x64! All dependencies incl. Framework are included.

• Portable releases are operating system and processor independent and they require .NET 10 Runtime on the target machine. For example, if you plan to use Boomi Console on a Mac or Linux machine.

Version History

5.9

• Uses .NET 10.0

• New Caching, fast as the light

5.7

• Connect.bat added to simplify installation and workspace setup.

5.6.x

• CODE PULL / CODE PUSH support

• SmartCopy fixes

5.5

• COMP SmartCopy implemented to support components templates

5.4.2

• FIX recurse parents

• FIX Dependent children

• NEW /workdir support

• Improved Deploy Exec support

• Improved cSet support

• New render template

• FIX: Components list with spaces

5.2.x

• cSet.jsonc files are also found relative to Workspace

• cSet.jsoncrender template added

• Fixing, fixing, fixing ...

• net9.0

5.1.3

• Fixed Templates to better support null-parameters

5.1.2

• FIX: Issues with the right folder when using /OutDir

• Removed default directories for Sets

5.1.0

Changes in the caching structure requires the cache DB to be deleted. Delete all bc.db.sqLite* files from your workspace. You will find one or three files!

• FIX rendering with workspace local templates, that override the global ones.

• FIX: The created readme.md is not always complete (race conditions).

• Building summaries refactored

  • Process summaries based on templates (no longer hard-coded)

  • Set summaries based on templates

  • Summary templates use Markdown and Atom links

• FIX: profile.db template

• CHG: All templates improved

• NEW: Support for Component Packages and Package Versions:

  • PACK GET, PACK DOC

• NEW: AppSettings support

  • Support for a dedicated Markdown directory

• CHG: The immutable Versions have got their on top level folder: .Version

• Performance improvements

5.0.x

5.0.3

• NEW: App Settings support

• Printing and Logging internal refactoring

• FIX: Process UML template (end statement)

5.0.2

• FIX: Workspace Templates

  • Packages -> Sets

  • Removed _Legacy

  • iPack.JsonC -> iSet.JsonC

• FIX: boomiConsole.user.json does not exist, prevents connecting workspace, when using BC for the very first time.

• FIX: Process UML

  • Process call UML supports multiple return paths

  • Better visualization for Goto statements

  • New color scheme

• FIX: Infinite loop in UML when process description has text w/o space longer than 60 characters

• NEW: Profile DB documentation uses template

5.0.0

• Property support

• Process Flow Diagrams

• Markdown Documentation

4.4.0

• Supports PackageVersion as Source

• Documentation updated, images restores

• New out folder structure

• Map documentation

• Reports improved

• Support for plain XML output

4.2.0

• Breaking Change Package getAction is no longer supported. Use getChildren="{None | Independent | Dependent | All} instead

• Fixed: Set BC_EXE Environment variables are set only in PROD environment.

• Template all DateSet contain a dataset element so that templaytes can check for the correct dataset (see Render DataSets):

<#if !dataset??>
	<#stop "dataset element is missing!">
<#elseif  dataset.name!="CompMetaDataSet"> 
	<#stop "Invalid dataset! Is the provided template compatible the with executed command?">
</#if>

4.1.5

• Fixed: Package getAction not respected

4.1.4

• Uses environment variables BC_DIR and BC_EXE

• Improved setup

• Initial Workspace and proivided batch files improved

• FIX: Local directory Workspace\Templaesno longer required

---

Previous Releases

23 April Rel. 1

• Fixed behaviour in case no /excludeFolders is provided.

23 January Rel. 2

• /excludeFolder option renamed to /excludePath

• When using /QueryFilter the excluded folders option is regarded. Components that are returned by the query (the query returns only component Ids) but whose directory is listed in the excluded directories are no longer queried and their metadata is no longer stored locally in the MetaDataCache. This saves a lot of time and it does not pollute the disk with components you don't want.

23 January Rel. 1

• Uses NET 7

• Deployment updated

Any comment suggestion or error report is welcome: Markus @ MarkusSchmidt.PRO