|Re: Add a new workflow pattern [message #1725468 is a reply to message #1725264]
||Thu, 03 March 2016 16:50
| Robert Brodt
Registered: August 2010
Location: Colorado Springs, CO
First, I'm sorry to tell you that this kind of nesting is broken with the current version of the editor, so please don't spend any more time trying to get it to work I am currently testing a fix for this problem and should have a new build by the end of this week, along with a working example.
Second, as you probably already know, in order for the editor to be able to distinguish a Custom Task from a plain BPMN2 Task, there MUST be some feature (either an extension attribute or element) in the task which your plugin defines. This feature must be set in the <tool> definition. For example the jBPM extension plugin defines a group of Custom Tasks that are identified by the extension attribute "taskName"; so the <tool> definition looks like this:
<tool name="Email Task" description="This is a Custom Task that can be configured to send emails">
I don't want to go into too much technical detail, but when the editor constructs the task from this tool, it first asks all of the extension plugins if they recognize it as a Custom Task; if so, construction and initialization is routed through the extension plugin's Model Extension mechanism.
On another topic: I'm curious about how and why you are using the BPMN2 Modeler, and why it was chosen over some other solution? I'm trying to build a case to present to my product manager, arguing against discontinuing development of this project, and any support from the community will help my case.
Powered by FUDForum
. Page generated in 0.01998 seconds