topic Re: In which release Designer is expected to support all BPMN 2? in Alfresco Archive

In which release Designer is expected to support all BPMN 2?

raj1 — Mon, 14 Mar 2011 14:40:10 GMT

Hello,In which monthly release of Activiti Designer can we expect all BPMN 2.0 elements to be supported…. Is it on the roadmap?Is there any developer forum where extension of the Signavio Modeler can be discussed or extension documentaiton and examples can be found?Please Guide me !!!!!!!!Raj

Re: In which release Designer is expected to support all BPMN 2?

trademak — Mon, 14 Mar 2011 19:29:10 GMT

Hi,

What do you mean with all BPMN 2.0 elements?
The Designer's goal is to support the functionality that is implemented in the Activiti Engine.
So as the Activiti Engine will support more elements of the BPMN 2.0 palette over time, the Activiti Designer will also support these additional elements.
What kind of elements would you like to see?

Best regards,

Re: In which release Designer is expected to support all BPMN 2?

mlisiewicz — Fri, 18 Mar 2011 14:03:29 GMT

It`s actually a very good question. I read activiti documentation very thoroughly.
I was planning to create simple process which would increment simple variable in a loop with 1 minute intervals. I have both Activiti Designer and Activiti Modeler installed.

In Activiti Desginer I was able to create fully functioning Service Task (Spring Bean), but i couldn't create very simple functionality of "Timer intermediate catching event" discussed in documentation: http://www.activiti.org/userguide/index.html#bpmnTimerIntermediateEvent

In Activiti Modeler it was opposite. I could easily create "Timer intermediate catching event" but no working Spring Bean…..(as this requires activiti:expression tag attribute not available in Modeler).

Can some one explain me how can i actually create a fully working process in editor?

Re: In which release Designer is expected to support all BPMN 2?

trademak — Fri, 18 Mar 2011 15:21:32 GMT

Hi,

If you describe the "Timer intermediate catching event" as very simple functionality you are of course very welcome to contribute this to the Activiti Designer.
You can create a fully working process in the Activiti Designer very well, but the timer intermediate catching event is just not yet supported in the current release.

Best regards,

Re: In which release Designer is expected to support all BPMN 2?

mlisiewicz — Mon, 21 Mar 2011 14:45:55 GMT

"Simple" wasn't proper word - I meant more like "essential".
Anyways,
"Timer intermediate catching event" can be temporarily exchanged with "Timer Boundary Event" attached to "Receive Task" - works for me.

P.S.
Road map (http://docs.codehaus.org/display/ACT/Roadmap) doesn't explain which release will cover which BPMN2.0 features, therefore such questions arise.

Cheers,

Re: In which release Designer is expected to support all BPMN 2?

mlisiewicz — Mon, 21 Mar 2011 15:35:12 GMT

What kind of elements would you like to see?

Nice to have:
- Timer intermediate catching event (probably one small step from "Timer Boundary Event")
- End Event terminating full process (not just execution)
- Timer Boundary Event missing essential attribute: cancelActivity="true/false"

for starter

Re: In which release Designer is expected to support all BPMN 2?

trademak — Mon, 21 Mar 2011 22:31:27 GMT

Okay, the additional timer events you mention are added in the Activiti 5.3 release, so now we can add those to the Activiti Designer. This will be added in the coming or the next release.
The end event terminate is not yet supported by the Activiti Engine and therefore also not in the Designer.

Best regards,

Re: In which release Designer is expected to support all BPMN 2?

mlisiewicz — Wed, 23 Mar 2011 15:06:14 GMT

Thank you for information.
As I go further into process development, I notice more "must have" elements.

- Parameters mapping in SubProcess and Call activity are crucial if we want to use these objects…

<callActivity id="callSubProcess" calledElement="checkCreditProcess" >
<extensionElements>
<activiti:in source="someVariableInMainProcess" target="nameOfVariableInSubProcess" />
<activitiut source="someVariableInSubProcss" target="nameOfVariableInMainProcess" />
</extensionElements>
</callActivity>