topic Re: From jpdl to bpmn 2.0, oh so verbose. in Alfresco Archive

From jpdl to bpmn 2.0, oh so verbose.

unsavory — Thu, 28 Jul 2011 18:07:43 GMT

I'm hoping someone has some pointers for me and can help me figure out how to model this process is a more efficient manner. I am porting our existing business processes from JBPM 4 to Activiti. Our old processes were written in jpdl, and now that I'm moving things over to bpmn, I am finding bpmn

Re: From jpdl to bpmn 2.0, oh so verbose.

trademak — Thu, 28 Jul 2011 19:07:34 GMT

Yes BPMN 2.0 is more verbose than jPDL. But this shouldn't be too much of a problem since there are tools like the Activti Modeler and Designer to simplify the generation of XML.
In addition there are ways to make it less verbose.
The user task you included can for example be rewritten to:

<userTask id="completeLangExamTask" activiti:assignee="${stringId}">
   <extensionElements>
      <activiti:formProperty id="TaskOutcome" variable="TaskOutcome" required="true" />
   </extensionElements>
</userTask>

And in jBPM you didn't set a form property, so no increase of verbosity there.
But again in the end, yes BPMN 2.0 is more verbose than jPDL.

Best regards,

Re: From jpdl to bpmn 2.0, oh so verbose.

unsavory — Thu, 28 Jul 2011 19:22:50 GMT

Yes, you are correct that in JBPM I didn't set a form property. The reason being is that in JBPM I had outgoing task transitions, I could take; something which has to be hacked into bpmn. And yes, I do consider it a hack.

Thanks for the pointer on the task assignment. I did see that in the documentation, but I prefer to stick with the bpmn conventions where possible.

I guess the way I am handling task transitions is the proper way of doing it and I will have to live with the verbose and complicated XML then.

Re: From jpdl to bpmn 2.0, oh so verbose.

ronald_van_kuij — Thu, 28 Jul 2011 20:45:52 GMT

Thanks for the pointer on the task assignment. I did see that in the documentation, but I prefer to stick with the bpmn conventions where possible.

You compare a totally proprietary format (jPDL) with a standard (BPMN) and then 'complain' the standard is to verbose. But at the same time do not 'accept' shortcuts which can if wanted be implemented more verbosely with exactely the same functionality… I don't get that. Sounds no valid reason to complain then 😉

I guess the way I am handling task transitions is the proper way of doing it and I will have to live with the verbose and complicated XML then.

The way you handle the transitions with the exclusive gateway is 'normal' but you still do not need to use a form property. I do not use the Activiti forms at all (use JSF) and just set a variable based on a button on a form that is clicked. So that part can be left out and the difference is even smaller then.