This is a customized / extended version of the open bpmn server. The extensions are:
-
a field for the source provenance of a data item
-
a field for the destination provenance of a data item
-
a field for Promela code that describes how task inputs get mapped / transformed into task outputs.
- These 3 new fields are in their own UI sub-panel for object properties. To get to this panel, double-left-click on the task in question. The object properties UI appears in the center bottom, with 2 sub-panels on the left side. The top is 'General'; the bottom is 'Verify_CWP'. Click on the top to set the task name and documentation. Click on the bottom to set any of the above 3 fields.
The .jar file in 'current-distribution' is only for Version 1.1.27 of the open BPMN VS Code extension; the new 1.1.29 version needs a new jar file built from source with the changes listed below.
New: CWP_VerifyServerLauncher (the source for a diff to apply to the original BPMN_ServerLauncher; about 4-5 lines) The original launcher is at Bpmn-CWP\open-bpmn\open-bpmn.glsp-server\src\main\java\org\openbpmn\glsp\launch
Bpmn-CWP\open-bpmn\open-bpmn.glsp-server\src\main\java\org\openbpmn\extensions\elements CWP_BPMNTaskExtension.java (the bulk of the extension)
Bpmn-CWP\open-bpmn\open-bpmn.glsp-server\src\main\java\org\openbpmn\glsp CWP_Verify_DiagramModule.java (called from the launcher for modified diagram support)
modified: Bpmn-CWP\open-bpmn\open-bpmn.metamodel\src\main\java\org\openbpmn\bpmn BPMNNS.java (enum with namespace type names) Bpmn-CWP\open-bpmn\open-bpmn.metamodel\src\main\java\org\openbpmn\bpmn\elements\core BPMNElement.java (a few methods to handle set/get for the 3 new fields)
There's a unit test file in Bpmn-CWP\open-bpmn\open-bpmn.glsp-server\src\test\java\org\openbpmn\glsp\utils that handles some 'empty filename' tests which fail on windows for some reason. I've removed them.
The top-level Maven project manages the builds of the 2 sub-projects - the Java BPMN metamodel and the Java server-side component (the client component is what you see in VS Code). Any Java IDE that supports Maven should be able to build it. The output jar file goes in the 'target' subdirectory of the server sub-project. The generated jar file name currently looks like this: open-bpmn.server-1.2.7-SNAPSHOT-glsp.jar, where 1.2.7 is a build version. This file name must be changed to imixs-open-bpmn.server-1.2.1-SNAPSHOT-glsp.jar in order for it to work as a server-side update to an installed VS Code open bpmn extension.
The above renamed jar file replaces the existing one of the same name in the 'server' subdirectory of the open-bpmn vscode extension directory. On Windows, this extension directory is in C:\Users{your_user_id}.vscode\extensions\open-bpmn.open-bpmn-vscode-extension-{version_#}\server .
Make a copy of the existing jar file in case of a problem, then delete it and copy the new renamed jar file in it's place. VS Code should start the server as before, and the graphical view of the BPMN network should appear as normal.