BAMOE provides a useful VS Code Extension that bundles graphical Editors for BPMN, DMN, and SCESIM files. The BAMOE Developer Tools for VS Code extension can be downloaded from the VS Code Marketplace.

Static file validation is available for BAMOE Developer Tools for VS Code. The Problems tab lets you see what is wrong with your file, both statically and when running it.

The DMN Runner, and Dev Deployments are not available for BAMOE Developer Tools for VS Code, however it is possible to get a similar experience of DMN Runner with the Test Scenario Editor.

For more information, see the following sections.

DMN Editor

In BAMOE Developer Tools for VS Code you can consume DMN files in the following ways:

DMN Editor:

dmn editor new

Since BAMOE 9.1.1, a DMN Editor is available. It is implemented with a modern technologies stack and native support of DMN 1.5 specifications.

The DMN Editor can open 1.2, 1.3, 1.4, and 1.5 DMN file versions, and it automatically saves them to DMN 1.5. If you are upgrading from a previous BAMOE version, for example, 9.0.x or 8.0.x, your DMN files will be automatically converted to DMN 1.5 version without any loss of logic.

DMN Editor (classic):

dmn editor classic

This is the classic version of the DMN Editor inherited from BAMOE 8.0.x. This editor can open 1.1, 1.2, and 1.3 DMN file versions only, and it saves them to version 1.2.

Note

The DMN Editor (classic) should be considered a deprecated tool. That means, no new feature will land in this editor version and it will be eventually removed in a future BAMOE version.

The DMN Editor is currently set as the default choice for DMN assets.

dmn editor switch version

Following are the steps to switch to the DMN Editor (classic):

  1. Right-click the currently opened DMN file tab.

  2. Select Reopen Editor with…​

  3. Select BAMOE DMN/Test Scenario Editors (classic).

  4. Select Configure default editor for '*.dmn'…​ in the same menu to change the default editor in your local machine.

Test Scenario Editor

Test Scenarios in BAMOE enable you to validate the functionality of business rules (for rules-based Test Scenarios) or DMN models (for DMN-based Test Scenarios) before deploying them into a production environment.

With a Test Scenario, use data from your project to set given conditions and expected results based on one or more defined business rules. When you run the scenario, the expected results and actual results of the rule instance are compared. If the expected results match the actual results, the test is successful. If the expected results do not match the actual results, then the test fails.

Note

The current version of the Test Scenario Editor does not support the DRL-based Test Scenarios at the moment.

In BAMOE Developer Tools for VS Code, you can author scesim files in the following ways:

New Test Scenario Editor:

scesim editor new

Since BAMOE 9.2.0, a new Test Scenario Editor is available. If you are upgrading from a previous version, for example, 9.0.x or 8.0.x, your *.scesim files will be compatible with the DMN Editor.

Test Scenario Editor (classic):

This is the classic version of the Test Scenario Editor inherited from BAMOE 8.0.x.

Note

The Test Scenario Editor (classic) should be considered as a deprecated tool, which means that no new feature will exist in this editor version and it will be removed eventually in the future BAMOE version. This editor parses DMN assets generated with the DMN Editor (classic) only (DMN version 1.2).

The DMN Editor is currently set as the default choice for scesim assets.

scesim editor switch version

Following are the steps to switch to the Test Scenario Editor (classic):

  1. Right-click the currently opened scesim file tab.

  2. Select Reopen Editor with…​

  3. Select BAMOE DMN/Test Scenario Editors (classic).

  4. Select Configure default editor for '*.scesim'…​ in the same menu to change the default editor in your local machine.

The scesim files produced by the new Test Scenario Editor can be used by the Test Scenario Editor (classic).