0.1.1 (alpha)

We are very happy to announce the second alpha release of Kogito Tooling!

This release features a new Chrome Extension that allows visualising and editing .bpmn and .bpmn2 files directly on GitHub's interface 🎉

We also updated the VSCode extension with some important fixes. See details below.

Chrome Extension

Features

• Open and edit BPMN and BPMN2 files directly on GitHub's interface.
• Commit or propose file changes directly on GitHub's interface.
• Use keyboard shortcuts like Ctrl+Z (undo), Ctrl+C (copy), Ctrl+V (paste). Note that on macOS you have to use Ctrl too, and not Cmmd. We are working on fixing that on the next releases.
• Use Full screen mode to edit large BPMN Diagrams. You can go back by clicking on Exit full screen at the top of the window.
• When you're editing a BPMN diagram, you can click on See as source to edit the XML manually. You can always go back to the diagram by clicking on See as diagram.

Known issues

• KOGITO-342 Check why BPMN editor shows error on page closing.
• KOGITO-347 Error logs happening during marshalling
• AF-2167 Native editor key bindings for macOS.

VSCode Extension

Features and fixes

• KOGITO-286 Fix VSCode editor path issues on Windows.
• KOGITO-226 Not all BPMN constructs (elements) are supported. If a non-supported construct is used, an error message will be displayed.
• KOGITO-293 Fix client-side marshaller to work with unsupported elements roundtrip.

Known issues

• KOGITO-155 Flicker when opening or restoring editors.
• AF-2167 Native editor key bindings for macOS.
• AF-2113 No indication of a modified BPMN diagram.
• AF-2168 No confirmation popup when closing a modified BPMN diagram.
• KOGITO-157 Copy/paste between different BPMN diagram.
• KOGITO-224 An error message is displayed if you try to create a new type by pressing Enter.
• KOGITO-225 Custom type definitions aren’t re-used within the diagram.
• KOGITO-272 Editor doesn't close when file is deleted.