All - KIE

Kogito Tooling 0.7.0 Released!

by Eder Ignatowicz - October 14, 2020 Tools News

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 connectingRead more →

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

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!

What is new on Business Central, from Foundation Team perspective — September 2020

by Eder Ignatowicz - September 21, 2020 Tools Article

We recently pushed many cool new features and bug fixes on Business Central added by Foundation Team. Those features are available at the 7.43.0 release. This post will do a quick overview of those. I hope you guys enjoy it! Dashbuilder Runtimes Since some release ago, we have introduced a new standalone application called Dashbuilder Runtimes. ThisRead more →

We recently pushed many cool new features and bug fixes on Business Central added by Foundation Team. Those features are available at the 7.43.0 release.

This post will do a quick overview of those. I hope you guys enjoy it!

Dashbuilder Runtimes

Since some release ago, we have introduced a new standalone application called Dashbuilder Runtimes. This new feature is a lightweight application able to run Business Automation dashboards created on Business Central in a containerized fashion, allowing us to cover many business automation use cases.

Soon we will publish a detailed introduction for Dashbuilder Runtimes.

Dashbuilder Runtime Embedded

On the 7.40.0 release, we improved the embedded capabilities of Dashbuilder Runtime, allowing users to embed a specific dashboard from an instance of Dashbuilder runtime on their web apps.

Every dashboard in the Dashbuilder runtime can be accessed in embedded mode and integrated directly on your application. See an example of this integration in a simple HTML page:

We also provided a new rest API that allows you to create a dashboard and query the dashboards and their pages on my Dashbuilder runtime instance.

It is possible to wrap the REST calls using a Javascript library published in npm: dashbuilder-js/api. With this API, you can use dashboards directly in your application. See examples in dashbuilder-js repository.

Soon we will publish a detailed post for Dashbuilder Runtime Embedded.

Dashbuilder Runtime Multi Dashboards Support

On the 7.42 release, we introduced a new feature on Dashbuilder Runtimes that allows users to import multiple dashboards on the same runtime instance.

The multi-mode is turned off by default. To turn it on, you must set the system property dashbuilder.runtime.multi as true.

Soon we will publish a detailed post for Dashbuilder Runtime Multi Dashboards support.

Dashbuilder External Components

How do I write my external component on Dashbuilder? In Business Central 7.43, we introduced a new way of creating your components in JavaScript and integrating them on dashboards.

External components are custom Dashbuilder page parts that users can develop to consume datasets from Business Central and display data any way users want. On community, we already have a lot of cool new external components, including a Heatmap for process and support for beautiful Victoria charts.

Soon we will publish a detailed post for Dashbuilder External Components support.

Other bug fixes and improvements:

We also fixed several bugs and made some performance improvements on Business central:

RHPAM-2808 : Making LRU cache configurable to avoid large memory retention
RHPAM-2957 : Business central doesn’t remember last used branch on logout
RHPAM-2737 : Testing on Project level fails if project was cloned via git/clone REST API removed and cloned again
RHPAM-2946 : Error when renaming an asset with pending changes
RHPAM-3134 : UI issue (in business-central) when more than one kie-server (with different ID) is connected.
RHPAM-2865 : Wrong created date on asset list
RHDM-1354 : NPE creating a project using Decision Central REST API and githook configured
RHPAM-3119 : [Data Modeler] Unsaved changes dialog appears after rename
RHDM-1378 : Issue re-importing a repository initially created by importing an empty repository in Business Central
RHPAM-3117 : Document upload doesn’t work on Windows

Thank you to everyone involved!

I would like to thank everyone involved with this release, from the excellent Foundation Team Engineers to the lifesavers QEs and all the UX people that help us make our work look fantastic!

Kogito Tooling 0.6.1 Released!

by Eder Ignatowicz - August 13, 2020 Tools Release

We just launched a fresh new Kogito Tooling release! 🎉 On 0.6.1 release, we made a lot of improvements and bug fixes. This post will do a quick overview of those. I hope you enjoy it! Kogito Tooling CI Improvements Since the beginning of the project, we have been using GitHub Actions to build kogito tooling repositories,Read more →

We just launched a fresh new Kogito Tooling release! 🎉

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

Kogito Tooling CI Improvements

Since the beginning of the project, we have been using GitHub Actions to build kogito tooling repositories, but last week we added three significant improvements for our CI/CD on this release.

Daily builds of our kogito tooling

Some days ago, we started doing an automatic daily release of the kogito tooling. The daily build of the Business Modeler can be accessed on this link and other artifacts (VS Code, Desktop, Hub, and Chrome Extension) can be downloaded in the latest “Publish daily dev version” job. This is a nice feature to try the latest master features of kogito tooling! 🚀

Business Modeler build for each PR

Also, to improve tests and code review processes, now for each PR on kogito-tooling instead of just generating the build artifacts, we are also providing a live version of Business Modeler.

To access the Business Modeler for a job fired by a PR in kogito-tooling, you can use https://kiegroup.github.io/kogito-online-ci/pull/<PR_NUMBER>

To access the Business Modeler for a job fired by a comment in the kogito-tooling issue, you can use https://kiegroup.github.io/kogito-online-ci/comment/<COMMENT_ID>

Build RHPAM Editors on kogito tooling actions

The BPMN, DMN, and Scesim editors used on Kogito are based on RHPAM editors that live on kie-wb-common and drools-wb Java-based repositories.

Another significant improvement that we did on this release is kogito-tooling GitHub Actions to do a full build on RHPAM editors and generate an integrated artifact (kogito tooling + editors from Java repositories).

Now, it’s just a matter of the author of a PR in kogito-tooling using a branch with the same name in his/her fork that contains changes in any editor (BPMN, DMN, or SceSim). As soon this happens, the “Pull Request CI — Full Downstream” job will run and produce a build of the VS Code extension, Business Modeler, Chrome Extension, and Desktop with the modified editors for faster testing.

But how should I build kogito tooling, if my editor change doesn’t affect the kogito tooling repository? Go to the pinned issue on the kogito-tooling repo and create a new comment following the format “Build: {github-username}/{branch-name}”.

In my opinion, those three improvements are a huge step forward for us. First, they will speed up a lot of our code review process and build, and, most important, it’s a big step forward in the path to continuous delivery of our lovely Business Modeler.

Kogito Tooling i18n

We’re happy to announce that Kogito Tooling is ready to be internationalized! This means that it will be possible to change the locale and access the Kogito Tooling Channels’ translations.

function MyComponent() {
 const { locale, setLocale, i18n } = useContext(myI18nCtx);
 const [name, setName] = useState("");
 return (
 <div>
 <p>{i18n.home.title} 🙂</p>
 <p>{i18n.home.body}</p>
 <input type={"text"} value={name} onChange={e => setName(e.target.value)} />
 {/* a couple of <br /> tags, just to give a better look to the example. */}
 <br />
 {/* `welcome` will always fallback on the 'en' dictionary because the ‘pt’ dictionary doesn't provide it. */}
 <I18nHtml>{i18n.welcome(name)}</I18nHtml>
 <br />
 <a onClick={() => setLocale("pt")}>pt</a>
 <br />
 <a onClick={() => setLocale("en")}>en</a>
 <p>{i18n.myCurrentLocale(locale)}</p>
 </div>
 );
}

view raw MyComponent.tsx hosted with ❤ by GitHub

We developed an i18n type-safe library with React usability in mind to enable this new feature, which allows simple and easy integration with an already existing project. See the full details on this blog post.

Page Support on OmniChannel Architecture

Since its inception, OmniChannel allowed us to run the same editor code in multiple channels without changing the codebase. Now we enhance this architecture also to support Pages and Components.

This new architectural component will enable many new use cases, as an example showing runtime screens, dashboards, etc. Stay tuned that soon we will launch a blog post and some examples of how to use it.

Auto start property for ad-hoc subprocess

We also added add “Auto Start” property to Adhoc sub-process properties panel, which is currently supported by the Kogito runtime via metadata.