- Support for Exclusive Jobs and Plugability of the Job Executor Infrastructure
- Persistent event subscriptions (infrastructure)
- Intermediate signal throw / catch
- Event based gateway
- BPMN transaction (cancel end event & cancel boundary event)
- BPMN compensation (compensation catch & compensation throw)
- Interrupting error event subprocesses
- (Multiple) message start events
- Various bug fixes
Find the full release notes here.
Special thanks goes to Camunda, and Daniel Meyer in particular for the some great core engine feature contributions.
Go download and taste this grand cru release!
I blogged about the BPMN 2.0 additions in more detail: http://www.bpm-guide.de/2012/03/01/activiti-5-9-introduces-more-bpmn-2-0-support/
ReplyDeleteThat's fantastic!!! Thank you to all the guys who worked on the new features.
ReplyDeleteWhat about the Eclipse Designer? Will it be updated to 5.9 in order to support the new features?
> What about the Eclipse Designer? Will it be updated to 5.9 in order to support the new features?
ReplyDeleteThis was one of the first things that came to my mind too when reading this great news...
activiti.postgres.upgradestep.58.to.59.engine.sql:
ReplyDelete58: update ACT_GE_BYTEARRAY set GENERATED_ = 0;
need:
update ACT_GE_BYTEARRAY set GENERATED_ = false;
Good morning,
ReplyDeleteI am a french student of the university of Poitiers and I am studing the BPM.
If you have some time for me it would be perfect but I know that you are currently very busy.
I am searching for some informations about the companies which use the Activiti BPM and it is for this reason that I write to you.
If you have some more informations for me it would be perfect.
Thank you for your response.
Best regards,
Paola KRUCH
Hi There,
ReplyDeleteI really appreciate your work on activiti , I am learning it as our bank ( cant tell the name) wants to use it as a lightweight BPM workflow engine.
But we are really stuck at 1 point of decision , A situation like below
We want to use activiti but only at very simple level of decision making (you can say 10 X 10 choices to make ) compared to other multipurpose & multi technologies decision flow.
SO I am definitely sure that we wont be requiring the whole engine or the all files that come into picture of execution
not even 20% of the engine...
We are stuck at one point where only an SME like you can resolve it:
Question is : Can we segregate the workflow engine into parts which we require and leave the rest (at installation or usage level) ?
I wanted to see it in user guides , but i cant find it there , Like Apache Tomcat provides a detailed design of how tomcat works, what are valves,pipes , Is there a guide explaining same (altough reading it will take a lot more time)
Can you tell me whether we can remove the other functionality and use only a single functionality which we want
Because , we will be repeating decision making 175000000 transactions per day and we are really curious about performace , because , if activiti run's as a whole software loads everything and calls everything to be ready ( not much of a lazy loader , which we want)
Then its better to have our on custom code developed to do the same (no harms ! b+ )
I can call you and explain the situation if you can provide me ur contact
But please , need your reply on this urgently (even if you have another BPM in mind , please suggest us)
In case you're not a bot, please do not crosspost and ask your question on the forum http://forums.activiti.org/en/viewforum.php?f=6
ReplyDelete