| how to enable customTasks in collaboration palette? [message #1087375] |
Thu, 15 August 2013 10:51  |
Marco Roque Messages: 16 Registered: July 2012 |
Junior Member |
|
|
Hello,
I've several custom Tasks that appear without any problem in the process type diagrams palette. However, i've tried using the same modelEnablement switching the enable properties from:
object: default
feature: Process
to:
object: default
feature: Collaboration
but it didn't work.
I've been searching for a way to this but i didn't find one.
What do i need to add a customTask to the palette in a collaboration diagram?
Thanks,
Regards
Marco Roque
|
|
|
| Re: how to enable customTasks in collaboration palette? [message #1087436 is a reply to message #1087375] |
Thu, 15 August 2013 12:31   |
|
Huh...funny thing. I just went through the code in BpmnToolBehaviourFeature and it looks like Custom Tasks are only added to the toolpalette for Process Diagrams - sorry about that!
Please file a bugzilla report for this, so I can get a fix out to you ASAP.
Thanks!
Bob
EDIT: You'll still have to create a <modelEnablement> section in your plugin.xml for Collaboration diagrams, similar to what you've (probably) already got for Process diagrams. Something like this:
<modelEnablement
runtimeId="my.runtime.id"
type="Collaboration" profile="Default Collaboration">
<disable object="all"/>
<!-- copy the enablements from "Collaboration" diagram type as defined in the "None" Target Runtime -->
<enable object="default" feature="Collaboration"/>
<!-- select the model extension features to be displayed in the Property Tabs -->
<enable object="Task" feature="taskConfig"/>
<enable object="TaskConfig"/>
<enable object="Parameter"/>
<enable object="BoundaryEvent" feature="isEnabled"/>
<enable object="MyEventDefinition" feature="value"/>
</modelEnablement>
[Updated on: Thu, 15 August 2013 12:37] Report message to a moderator
|
|
|
|
|
|
|
| Re: how to enable customTasks in collaboration palette? [message #1090799 is a reply to message #1089369] |
Tue, 20 August 2013 12:59  |
|
Yikes! Sorry about that. Am I correct in assuming you are using the Juno version of the editor? I just tried a "smoke test" with that platform and found the problem was caused by a bad code merge. I'm usually pretty good at testing these things before publishing a nightly build, but this one just slipped past me 
I'll have a new build by end of today that you can test with.
Thanks for testing!
Bob
|
|
|
Powered by
FUDForum. Page generated in 0.01828 seconds