Thursday, 2 December 2010
Wednesday, 1 December 2010
- 85 pages of documentation
- Super easy demo install that gets you up and running in less then a minute
- Easy embeddable (just include the .jar)
- Excellent Spring integration (contributed by SpringSource)
- Support for all common BPMN 2.0 elements
- Easy to link any type of Java to process steps
- Event listeners
- Transactional timers
- Audit trails
- Flexible transaction management
- Extremely fast / minimal execution overhead
- Full Query API
- REST interface
- Easy task management
- Starting new process instances
- Claiming group tasks
- Starting processes andcompleting tasks with or without forms
- Easy deployment of forms with processes
- Operational management console
- Managing deployment
- Business archive file upload
- Managing jobs
- View database table contents
- Contributed by Tijs, Ron, Tiese and Yvo from Atos Origin
- Eclipse plugin
- New Activiti project and diagram wizzards
- Graphical process modeling
- Form support for Activiti extensions
- Pluggable activity types! Fully documented!
- Unit test generation
- Validation with errors showing in Eclipse Problem view
- Contributed by Camunda
- BPM collaboration done right
- Spans business users, developers and system admins
- Repos: Activiti Modeler, SVN, JIRA, File system
- Linking of artifacts in repos
- Pluggable actions depending on the artifact type
- Contributed by Signavio
- Web based graphical BPMN 2.0 authoring
- Saves models in a shared file based repository
- Very intuitive to use!
Saturday, 30 October 2010
<bean id="dataSource" class="org.springframework.jdbc.datasource.TransactionAwareDataSourceProxy">
<bean id="transactionManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
<property name="dataSource" ref="dataSource" />
<bean id="processEngine" class="org.activiti.spring.ProcessEngineFactoryBean">
<property name="databaseType" value="h2" />
<property name="dataSource" ref="dataSource" />
<property name="transactionManager" ref="transactionManager" />
<property name="dbSchemaStrategy" value="drop-create" />
<property name="deploymentResources" value="classpath*:/org/activiti/spring/test/autodeploy.*.bpmn20.xml" />
<bean id="repositoryService" factory-bean="processEngine" factory-method="getRepositoryService" />
<bean id="runtimeService" factory-bean="processEngine" factory-method="getRuntimeService" />
<bean id="taskService" factory-bean="processEngine" factory-method="getTaskService" />
<bean id="historyService" factory-bean="processEngine" factory-method="getHistoryService" />
<bean id="managementService" factory-bean="processEngine" factory-method="getManagementService" />
- Activiti Probe added Job and Deployment management
- Event listeners
- Query for process instances based on variable values
- Parameterized method expressions
- History details and audit capabilities
- Extracted FormService and improved flexible form handling
- Activiti config file from properties to xml
- PostgreSQL en Oracle support
- Improved DB performance by fine tuning indexes
- Check out all 62 Jira issues of this release
Friday, 1 October 2010
Thursday, 30 September 2010
- Added Activiti Designer, an eclipse plugin for process authoring targetted for developers
- Design BPMN processes grafically: start event, end event, sequence flow, parallel gateway, exclusive gateway, embedded subprocess, script task, user task and service task.
- Generate JUnit test case by right click on the process in the package explorer
- Run the JUnit test with an embedded h2 database
- Configure Java class for a service task
- Configure assignee or candidate for a user task
- Configure script with a script task
- Added DB support for MySQL and PostgreSQL
- Activiti Modeler and Activiti Engine are now synced on the final BPMN 2.0 specification
- New improved version of Activiti Modeler
- Loads of Activiti Cycle improvements
- Added JDK 5 compatibility
- Added history activity instances
- Added unit testing support
- Added email support and receive activity
- Added optimistic locking for out-of-the-box clustering support
- Added more query APIs
- Minor API cleanup
Friday, 24 September 2010
Thursday, 23 September 2010
Monday, 20 September 2010
Monday, 13 September 2010
I would like to announce the Grails Activiti Plugin 5.0.beta1 Released.
Grails Activiti Plugin is created to integrate Activiti BPM Suite and workflow system to Grails Framework.
With the Grails Activiti Plugin, workflow application can be created at your fingertips!
* Update Activiti's jar files and examples to 5.0.beta1.
* Introduced Dependency Injection for RuntimeService, RepositoryService and HistoryService (API Update).
You can find out more about this plugin at following links:
* Project Site and Documentation: http://code.google.com/p/grails-activiti-plugin/
* Support: http://code.google.com/p/grails-activit ... ssues/list
Well, done, Chee!
Wednesday, 1 September 2010
I liked the potential of the collaboration environment to bridge the gaps when rules and process are both being used in a solution and I also liked the potential of applying content management to business rules. Interesting ideas both of them and I look forward to learning more.
- Sandy Kemsley, renowned BPM analyst, wrotea an objective analysis of the Activiti platform. She is eager to see how Activiti will evolve. And we won’t dissapoint her.
- BPM expert Scott Francis of BP3 wrote a very motivating blogpost. He actually downloaded the distribution and played with it. Let me quote him a few times here
- “Did I mention that the whole stack ran just fine, natively, on my Mac as well as a Windows VM?”
- “The documentation is already pretty comprehensive, and gets down to no-nonsense details (not true for many commercial products).”
- “I think the market is ripe for an open source BPM platform that leverages standard underlying technologies and is built from the beginning to allow for cloud-based deployment”
- “We may end up investing some time in the project ourselves.”
- The 451 Group posted a spot-on business analysis of the announcement, and let me quote them:
Activiti is likely to shake-up the BPM market with a ubiquitous project that supports the BPMN 2.0 standard from the Object Management Group.
- Peter Hilton from Lunatech Research, hits the nail on the head:
business processes and work-flow are aspects of most business software and integratingembeddable BPM will be a key element in reducing the cost of business software development.
- Theo Priestly asks the question everybody wanted to ask: “has the fight for open-source dominance begun?”
Thursday, 26 August 2010
Thursday, 19 August 2010
That is a really good metaphore for the typical traditional BPM player: Inert, not in the shape that it once was but it's floating.
That's Activiti: New, fast, agile and fun to work with!
Wednesday, 4 August 2010
- MySQL support
- Support for method expressions on sequence flow
- Revised ActivityExecution API
- Added ConcurrencyController API
- Process Event Bus
- Taskforms: added date and date picker support
- Explorer: changed process definition drop down list to a separate page
- BPMN parallel gateway
- BPMN manual task
- BPMN (embedded) subprocess
- BPMN call activity (subprocess)
- BPMN Java service task
- Spring integration (experimental, no docs yet)
- Made engine compatible with BPMN 2.0 beta process models
- Fixed exception on windows and linux when using boundary timer event
- Expression cannot have whitespaces
Monday, 19 July 2010
Tuesday, 6 July 2010
Monday, 5 July 2010
- Alfresco: Core engine technology and BPMN
- Mimacom: Core engine technology and task management
- SpringSource: Making the designs DI friendly and general solid software design expertise
- Camunda: BPMN and practical BPM collaboration
- Next Level Integration: DB compatibility and high scalability
- MuleSoft: Web services and ESB expertise
Wednesday, 30 June 2010
- BPMN Timers
- BPMN JSR 223 script support.
- Switched from iBatis to MyBatis
- Updated to a newer version of BPMN xsd
- Query API
- Switched JUnit usage from 3-style inheritance to 4-style annotations
Monday, 28 June 2010
Make Business Process Management (BPM) ubiquitous
by offering solutions
that both business people and developers love.
Thursday, 24 June 2010
We are very excited because Mimacom brings in this mix a vast amount of expertise on building the Edorasware process engine. That core process engine knowledge and Mimacom's serous commitment to participate will result in a significant acceleration of Activiti's progress.
Wednesday, 23 June 2010
Saturday, 19 June 2010
Wednesday, 9 June 2010
BPM as a management discipline is the responsibility of every strategic executive manager. It's to ensure that the organization performs well in their core business processes. This involves understanding what values the organization delivers and how those are achieved. This means analyzing, documenting and improving the way that people and systems work together. As part of that work, it's useful to work with models and diagrams. BPMN diagrams express the execution flow of the steps to accomplish a certain goal. Important to note that these models are used for people to people communication. They can be underspecified, which means that they can contain valuable high level information without including unnecessary details. Such underspecified process models are also known as abstract business processes.BPM as software engineering means that executable business processes will be executed by a BPM System (BPMS). Executable business processes are based on a diagram that represents the different steps in an execution flow. The diagram can actually look exactly the same as the abstract business process. But executable business processes are different in some very fundamental ways. First of all they need more technical details. That part is generally accepted.
Tuesday, 8 June 2010
Wednesday, 2 June 2010
- Task forms
- Database table content viewer in Activiti Probe
- BPMN 2.0 Exclusive gateway
- Unified Expression Language support
- Reduced download size (37MB --> 18.5MB, removed duplicated libs)
Thursday, 27 May 2010
Wednesday, 26 May 2010
Monday, 24 May 2010
The rest of that post is rather poor in terms of facts. He says
we’ve got no issue with the jBPM team moving to greener pastures to try and rescue a moribund open source project
Above all, BPM is a management discipline. As our CTO Michael Rowley is fond of saying, BPM can be done with pens, whiteboards and Post-It notes.They probably didn't take the time to go through our website. In our very first FAQ "What is BPM?" in which we clearly distinct between BPM as a management discipline and BPM as software engineering:
BPM as a management discipline is the responsibility of every strategic executive manager. It's to ensure that the organization performs well in their core business processes. ... This means analyzing, documenting and improving the way that people and systems work together. As part of that work, it's useful to work with models and diagrams. ... Important to note that these models are used for people to people communication. ...
BPM as software engineering means that executable business processes will be executed by a BPM System (BPMS). ...
The idea of the process virtual machine is simple and appealing
The idea is that all of the hard work of developing a process engine can be put into a layer that is more general and abstract than any process definition language. Then, when anyone wants to create a process engine based on a new language, it is a simple matter to map the concepts of the new language onto the constructs of the PVM and voila: a new process engine!
You can use the ActiveBPEL engine under GPL v2 by downloading it from this website. Alternatively, you can acquire a Commercial License to Active Endpoints' ActiveVOS Enterprise product by contacting Active Endpoints.
A traditionally developed BPMS will be on top of an application server and a database. The application server is on a JVM, which is on an operating system, which often is on top of a virtual machine. Every layer adds value but it also adds cost ... Is the cost/benefit tradeoff right for a PVM layer?
I’d say no.
Thursday, 20 May 2010
Savio raises the point
On one hand, the JBoss Application Server, an LGPL licensed product, has garnered strong downloads and continues to grow revenue at a faster pace than Red Hat’s Linux business. It would seem that the LGPL hasn’t been a hindrance to JBoss Application Server adoption. On the other hand, as Newton points out, some ISVs, and as I’ve heard, some customers, remain concerned about viral licenses. While the LGPL was created to specifically address the viral nature of the GPL, some ISVs and customers remain weary.To me, the most important difference between the LGPL and Apache license is summarized in: "some customers remain concerned about viral licenses"
I agree with a lot of points that Bill makes in response:
the OSS license chosen for a project is not that important as far as adoption or business goes. The most important driver for OSS is and always has been the brand of the project. Like their commercial counterparts, how the project is perceived by consumers is what drives both adoption and business. So, I agree, LGPL doesn’t add a lot of value.
If you boil it down, the distinctions betwen GPL, LGPL, and ASL are pretty much meanlingless to most consumers of OSS. How so? ...I would rephrase those 2 quotes as "Brand and credibility is the most important aspect to an open source project, followed by the license".
But then I think Bill goes overboard on
The whole push by Apache.org and its minions that ASL is the one true license is just damaging to open source.I'ld like to clarify that we don't consider Apache to be the one true license. It happens to be the license that allows us to exploit our brand and credibility, without being hindered by some customers' LGPL concerns (even if they would be unjustified). So it's more a practical choice instead of a religious one.
Back in 2003, a group of JBoss contributors tried to fork both the JBoss code base and the JBoss business. ... We then come full circle to 2010 with history repeating itself (well, sort of). You have Tom Baeyens leaving Red hat for Alfresco to create a competing BPM engine.
If you are an Apache guy, you should be appalled by behavior like this when it happens. Individuals and companies that use ASL as a weapon to further their own selfish and commercial needs should be castigated...
As for LGPL vs. ASL? I could care less, it really doesn’t matter.
You don’t see JBoss caring so much either.My experience was different ;-)
Anyways, I agree with your last statement:
Anyways, have fun with this, and remember taking any one position to seriously is unhealthy.
Monday, 17 May 2010
Tuesday, 11 May 2010
- High cost of setup. This implies getting the software up and running and also get all people up to speed with the technology.
- High cost of integrating the BPM system with the outside world. Web services or even specific adapters for communicating with other applications results in a significant threshold.
Wednesday, 31 March 2010
We're already seeing a big momentum around BPMN 2.0. And us bringing a BPMN 2.0 OSS offering will help spread the knowledge and adoption beyond the critical mass.
For other OSS technologies like ESB's or appservers this happened late in the game, long after proprietary vendors had settled themselves. Typically the advent of an OSS offering started making the technology a commodity. Proprietary vendors are then pushed to produce more features on top of what is commodity in order to keep making money.
So it's going to be interesting to see what happens if we're one of the first native BPMN 2.0 solutions.
If you're interested in Business Process Management (BPM), then this new development is really important. Both OSS and proprietary vendors are embracing a single technology for BPM. That is a huge step forward from the past where previously all the pure-play BPM solutions were based on different concepts and proprietary languages. Going forward, the language choice will be easy.
One technology can be used by both non technical business people and developers. And when OSS enters the BPMN 2.0 space, you'll have more choices of products. On the one hand, the initial treshold to get started gets lower with OSS for the masses being freely available. And on the other hand you'll see more features in the proprietary offerings if you want to pay for it.
Monday, 29 March 2010
That's all we can share at this point. Keep posted for more information.
Friday, 29 January 2010
Other recent presentation materials on jBPM:
Friday, 22 January 2010
Tuesday, 19 January 2010
At Camunda, they have a lot of experience on how to bring BPM into practice. There is a lot more to it then just using a BPM product. This book provides simple guidelines so that any company can benefit from the real power of BPM.
The rest of the world can only hope that it gets translated soon :-)
Friday, 15 January 2010
The rules deployer is a convenience integration between jBPM and Drools. It allows for unified deployment of processes, rules together with forms and other process resources in a .bar business archive. jBPM creates a KnowledgeBase based on all .drl files that are included in a business archive deployment. Activities like the rules and rules-decision leverage this KnowledgeBase.
A rules-decision will take a single outgoing transition based on the evaluation of rules. Let's first look at a rules-decision example process:
This is the RulesDecision jPDL process file (click to enlarge) :
Now all you have to do is deploy the following .drl file together with the process in a .bar business archive and deploy it to jBPM (click to enlarge)
For your convenience, the process variables are made available as global variables in the rules. Then you can start a new process instance with jBPM like this (click to enlarge):
And your rules will be used to evaluate which outgoing transition will be taken in the process execution. Voila. That's all there is to it.
Similarly, a rules activity will evaluate rules, allowing them to update process variables or perform other actions. Let's look at a rules example process:
The Rules jPDL process file looks like this (click to enlarge):
Imagine a process variable of type Room (click to enlarge)
And a rule like this (click to enlarge)
Then starting a new process instance like this (click to enlarge):
will execute the activity, evaluate the rule and update the room process variable.
Wednesday, 6 January 2010
We just released jBPM 4.3. This release includes the first part of our BPMN 2.0 language implementation. Check out the online docs http://docs.jboss.org/jbpm/v4/devguide/html_single/#bpmn2
More details about BPMN on Joram's blog.
Highlights for the jBPM 4.3 release:
- Added BPMN 2.0 runtime engine!
- Extended java activity with ejb method invocation
- Added jms activity (including test facilities)
- Added integrated rules deployment and activities rules and rules-decision
- Added enhanced spring integration and created continuous integration for it
- Automatic saving of updated deserialized variables
- Added count() capabilities to all queries in the api
- Fixes various bugs