Kogito Tooling 0.7.0 Released!

We just launched a fresh new Kogito Tooling release! 🎉

On the 0.7.0 release, we made a lot of improvements and bug fixes. This post will do a quick overview of those. I hope you enjoy it!

Backend support on Kogito Tooling

We introduced Backend support on Kogito Tooling. Developers can now augment their editors’ capabilities by connecting backend services through an infrastructure included in Kogito Tooling.

Lots of possibilities of executing code outside the client are enabled/facilitated with this new infrastructure, such as calling a java local backend service, reaching an HTTP endpoint, triggering a command in the terminal, to name a few.

Soon, this infrastructure will allow many new use cases, including auto-complete via Java Language Server, DMN/BPMN validations, Scenario Simulation executions, etc.

An experimental Quarkus app service on the VS Code channel. The server is started up and stopped by the infrastructure as soon as the extension is activated or deactivated. Keep in mind that the extension is activated when the first diagram is opened and deactivated only when the VS Code is closed.

See full details of this important innovation in this blog post from Guilherme Caponetto.

DMN — Read-Only mode

We introduced a read-only version of our DMN Editor that will be really useful during PR reviews and also in your future embedded editors. Take a look at this feature on our chrome extension:

DMN — Multiples Decision Requirement Diagrams

On 0.7.0, we are also introducing a tech preview support for Multiple DRDs. For complex DMN models, you can now use the DMN modeler to design multiple DMN decision requirements diagrams (DRDs) representing parts of the overall decision requirements graph (DRG) for a DMN decision model.

This improvement enables you to better organize DMN decision models with many decision requirements by dividing the model into smaller nested DRDs.

Check this post to understand this feature in detail.

Notice: in some use cases, when your DMN model contains multiple decision requirements diagrams, you may face some validation errors that prevent the execution. You can put the kogito.decisions.validation=DISABLED property into the application.properties to disable model validation and successfully execute the model. This issue won’t be present on Kogito Tooling 0.7.1 (end of October) — KOGITO-3571.

DMN — PMML support

We also added on DMN Editor, a new feature that enables PMML file imports inside DMN Editor. In a similar way we import external DMN files.

A PMML file can be linked to a DMN file using the “Included Model” tab. Pressing the Include Model button, a popup with a selection box containing all PMML and DMN files inside the same directory of the opened DMN file should appear.

BPMN — Script Syntax Highlight

The process designer now provides syntax highlighting and error checking capabilities when working with scripts, for example, in the case of a Script Task.

BPMN & DMN — Inline Text Editing

Node name editing has been made more fluid with the new Inline Editor. It is possible to edit text directly on the nodes without floating boxes or confirmation buttons by double-clicking any node. For applying changes just hit “Enter” or click outside of the node and for canceling hit “Esc”, while editing.

Fixed issues and improvements

We also made a lot of refactorings and improvements, especially to allow our internal APIs’ extendability.

Infrastructure

  • [KOGITO-3313]: Fix on filename change
  • [KOGITO-3326]: Enable EmbeddedEditor to support an update on the StateControl instance
  • [KOGITO-3417]: EditorEnvelopeView reference should be get with a function to be updated
  • [KOGITO-1508]: Implement selenium test for kogito-bpmn in community
  • [KOGITO-1517]: Improve accessibility on file with unsupported extension error
  • [KOGITO-3042]: Replace MessageBusClient with proxified version of ApiToConsume
  • [KOGITO-3043]: Provide locale information in a way that GWT can read
  • [KOGITO-3056]: Move I18nService and and its Envelope/Channel APIs to its own module
  • [KOGITO-3057]: Add a initialLocale prop on I18nDictionariesProvider

Editors

  • [KOGITO-2060]: [Test Scenario Editor] Order of facts of Test Tools in Kogito and BC is different
  • [KOGITO-1716]: [Test Scenario Editor] Show warning if user opens scesim file for rule based test scenario in VSCode
  • [KOGITO-3155]: [Test Scenario Editor] Test DMN model including PMML
  • [KOGITO-3153]: [DMN Designer] PMML support — run via Quarkus
  • [KOGITO-543]: [DMN Designer] Read Only mode
  • [KOGITO-2664]: [DMN Designer] Multiple DRDs support
  • [KOGITO-3419]: [DMN Designer] None example of importing models in kie-dmn-core opens in editor
  • [KOGITO-3504]: Interrogation mark cannot be used on new inline editor

VS Code

  • [KOGITO-3314]: Broken link on popup due to circular dependency issue
  • [KOGITO-2984]: Use i18n dictionaries on VS Code extension backend
  • [KOGITO-3205]: Create test runner service running on the backend infra

Business Modeler Preview

  • [KOGITO-3336]: On Business Modeler Desktop the sample files are named as “unsaved file”
  • [KOGITO-2835]: Online — Update ‘edit existing file’ to use the FileUpdate component

Known issues

  • [KOGITO-3571]: [DMN Designer] Multiple DRDs support — Information requirements are duplicated into the DMN XML

Further Reading/Watching

If you are curious about the history of Kogito Tooling and how we created this technology, I would like to recommend two links for you:

Thank you to everyone involved!

I would like to thank everyone involved with this release from the awesome KIE Tooling Engineers to the lifesavers QEs and the UX people that help us look awesome!

This post was original published on here.
0 0 vote
Article Rating
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments