Wednesday, September 2, 2015

Activiti 6 Beta 1 released

Today is a big day for the Activiti project and community. We released the first beta of the first major revision of the Activiti Engine.  The main reasons to introduce Activiti 6 are:

  • Complete backwards compatibility with version 5: database-wise, concept-wise and code-wise.
  • Rewrite of the core engine: direct execution of BPMN 2.0 (vs transformation to intermediate model)
  • Simpler and cleaner runtime execution data structure, where predictability of the structure is crucial
  • Decoupling of persistence layers for future possible different implementations
We also introduce a new test application to work with the Activiti Engine, that replaces the Vaadin Explorer application. The new application is just named Activiti app and uses Angular JS. It contains a lot of the Explorer functionality but there are some differences:
  • We introduced a new form editor that allows you to design task and start forms using a visual editor. There are also quite a couple of additional form field types.
  • There's a new task UI to start process instances and work with tasks.
  • There's a new concept of app definitions. App definitions is a grouping of process models and forms that can be deployed on the Activiti Engine. Each deployed app can be made available on the user dashboard.
We very much welcome any feedback on this first beta release and in specific testing the Activiti 5 backwards compatibility with your process definitions would be great. 

A couple of standard warnings about a beta release. It's not meant to be used in production and we didn't focus on performance yet.

We'll do more blog posts in the next days and weeks to talk about more details of Activiti 6. In the meantime please give feedback and help to get Activiti 6 stable and well tested!

Monday, August 10, 2015

Activiti Designer 5.18.0 released

Today we released Activiti Designer 5.18.0. This release contains the following highlights:
  • Updates to BPMN palette with support for compensation and cancel events and transaction sub processes. We also added missing signal and message event elements.
  • The Activiti Designer now supports Eclipse Kepler and Luna. Let us know if you want us to support Eclipse Luna and Mars instead.
  • Better handling of pools and lanes and sub processes with move and resizing. Bendpoints are moved on resize and move of containers as well.
  • Messages and signals are now defined on process root level and can be selected for message and signal events.
  • Internationalisation support for element labels. You can define multiple languages in the Eclipse preferences and label fields will be made available for each language.
  • Lots of bug fixes.
This release has been long overdue and we'll make sure to keep updates coming on a lot faster schedule starting from this release. Help in raising bugs, thinking of feature requests and of course pull request are very welcome.

Friday, July 31, 2015

Activiti 5.18.0 released

Today we have released Activiti 5.18.0! We are really happy to provide the new bulk insert and other improvements to the Activiti Engine starting from today. 

This release took a bit longer than expected because we have been working on Activiti 6 in parallel. We announced Activiti 6 on our well attended Paris community event. We expect to ship an alpha release of Activiti 6 at the end of August.

You can also expect a new release of our Activiti Designer in the next couple of weeks. 

So what's new in Activiti 5.18.0?



  • We enhanced the OR query support, it's now possible to use multiple OR parts in one query
  • Improvements to the async executor we introduced in Activiti 5.17.0. There were some cases that could result in deadlock exceptions and that's resolved in this version.
  • Improvements to the Activiti Modeler with terminate end events, cancel event and transaction support, and more intermediate catch and throw event support. Also, improvements to interrupting and non-interrupting solid and dashed line for boundary events.
  • Upgraded Spring dependency version to 4.1. Activiti is still working with Spring 4.0.x and 3.x as well.
  • Various bug fixes
For more information you can read the release notes.

Enjoy the release.


Tuesday, April 7, 2015

Activiti JIRA moved to Atlassian Cloud

As you might have seen, Codehaus is shutting down. Since we heard about this we have been looking for the best alternative solution for the Activiti issues. Because we wanted to keep the existing issues as much as possible, an hosted JIRA solution made the most sense. Atlassian is offering a free hosted JIRA instance for open source projects and we are grateful that our application for an Activiti JIRA instance got approved.

Since export options are limited on Codehaus we are not able to migrate all data associated with each issue. For example, attachments and comments are not exported. If you could help us to add attachments and important comments back again that would be a great help.

You can find our new JIRA system on https://activiti.atlassian.net. You need to create a new account before you can access the Activiti JIRA. All issues should still have the same key so it should be easy to find your old issues again. Reporter information has been migrated to the new JIRA, but only as reference information and therefore it won't be coupled to your account by default.

Performing such a migration always means we lose some information and it's a painful process for every user involved. But sadly we didn't have much choice. I hope everyone will create a new user account and will help us to get important issues updated with the correct information as much as possible.

Thursday, December 18, 2014

Activiti 5.17.0 released

I'm happy to announce the immediate availability of Activiti 5.17.0. This release contains the following highlights:
  • We introduced a fully tested and brand new Async executor, which supersedes the old Job executor. The new Async executor uses less database queries to execute asynchronous jobs and is more performant in general. By default the Activiti Engine still uses the old Job executor, so you have to explicitly choose for the new Async executor by setting the asyncExecutorEnabled property in the process engine configuration.For more details you can look at the advanced section of the user guide.
  • The Activiti Modeler is fully revised and is implemented using Angular JS. This is donated from the Alfresco Activiti BPMN editor that's part of the Alfresco Activiti Enterprise offering. The new Angular JS Activiti Modeler is LGPL licensed.  Note that some dialogs are not yet ported to the new Activiti Modeler, but you'll also find quite a bit of new functionality, including Mule and Camel tasks and being able to define a sequence flow order for an exclusive gateway. Any help with adding new features is really appreciated.
  • The user guide has been revamped with a rewrite to AsciiDoc
  • It's now possible to start a process instance a skip tasks based on a skipExpression. This is very handy when you are migrating process instances to the Activiti Engine (thanks to Robert Hafner for the pull request).
  • We added a new module named activiti-jmx to the Activiti project, which enables JMX for the Activiti Engine. Read Saeids blog for more details (thanks Saeid).
  • Variable fetching has been optimized for process instances and executions in general.</li>
  • The database upgrade scripts use a different minor version than the JAR version. With the 5.17.0 release, the database version is 5.17.0.2. This versioning enables us to release snapshots and still be able to upgrade from a snapshot release to a stable release. For a 5.17.1 release the database version will be 5.17.1.x where x can be any number. So only the last minor version number can differ from the Activiti Engine release version.</li>

Thanks to all community members for their contributions to the Activiti project in the last months, and especially Robert Hafner and Saeid Mirzaei. Enjoy the new release!

Friday, October 17, 2014

Activiti 5.16.4 released

We've released Activiti 5.16.4 and that includes bug fixes, but also 2 bigger features.

We've introduced a new lock free job executor that improves the scalability of the job execution with magnitudes. You can read more about the new job executor here https://github.com/Activiti/Activiti/wiki/Notes-on-the-new-Actviti-Jobexecutor-(Oct-2014).
Note that the default job executor is still the old job executor, so you need to explicitly enable it before it will be used. The new job executor only supports non-exclusive jobs right now. Exclusive job and suspended process instance support will be added in the next Activiti release.

Another change is the move from the Restlet framework to the Spring MVC framework for the REST services implementation. The REST API urls haven't changed though, so all REST clients should still be working ok. We did remove the deprecated legacy REST services though. Let us know if you run into issues due to this removal, but all data should be available through the other REST services. A benefit of moving to Spring MVC is the integration with Spring Security, so it's easier to configure authentication. Also, we'll be introducing an Activiti Spring boot module in the next Activiti release, which makes it easy to add Activiti to a Spring boot application. You can already see more info here http://www.jorambarrez.be/blog/2014/09/29/webinar-on-youtube/ .

You can get the new release via Maven central, the download page on the Activiti website, and our Activiti Github repository. Enjoy!

Friday, August 15, 2014

Activiti 5.16.1 released

Today we released Activiti 5.16.1. This is mainly a bug fix release for Activiti 5.16 and doesn't include any database changes other than the usual version update in the property table.

Although it's a bug fix release, we've added a nice new query capability for process instances and tasks, an OR statement. Now you can query for process instances and tasks using one chain of OR statements using our query API. It can be used like this:

runtimeService.createProcessInstanceQuery()
     .or().processDefinitionKey("test").processDefinitionName("Test").endOr().list();

But you can of course also mix with AND statements like:

taskService.createTaskQuery().taskNameLike('%Test%')
     .or().taskOwner('kermit').taskAssignee('kermit').endOr().list();

This will result in a query like:

WHERE task.name like '%Test%' AND (task.owner = 'kermit' OR task.assignee = 'kermit')

Current limitations of the or construct are:
  1. You can use only one chain of OR statements right now. So you can't use the or and endOr methods more than once.
  2. You can use a specific field only once in an OR statement, so you can't use processDefinitionId twice in an OR statement for example. Only the second value will be used in that case.

We welcome any feedback and suggestions on this new query API option. If we get positive feedback, it will be added to more query APIs for the next release. Enjoy!