License

All the software included in this distribution is distributed under Apache license V2 unless for these exceptions:

Documentation

Links

A more elaborate collection of Activiti-links can be found on the Activiti Community page

Activiti Release Notes

Release Notes - Activiti - Version 5.17.0

Highlights

Release Notes - Activiti - Version 5.16.4

Highlights

Implementation changes

Release Notes - Activiti - Version 5.16.1

Highlights

Release Notes - Activiti - Version 5.16

Highlights

Bug fixes and various smaller improvements

Check out the Release notes for more details

Bug

Improvement

New Feature

Wish

Release Notes - Activiti - Version 5.15.1

Highlights

Release Notes - Activiti - Version 5.15

Highlights

Bug fixes and various smaller improvements

Check out the Release notes for more details

Sub-task

Bug

Improvement

New Feature

Task

Release Notes - Activiti - Version 5.14

Highlights

Important Note for MSSQL and DB2 users

Activiti 5.13 and 5.14 contain changes to the default indexes that are created when using MSSQL or DB2 as database. These indexes are not created automatically when upgrading Activiti, as they may conflict with custom indexes or impact the database load. The purpose if the indexes is to avoid deadlock exceptions when using Activiti under high load.

As such, please review carefully following commits and apply to your database (where applicable):

Bug fixes and various smaller improvements

Check out the Release notes for more details

Bug

Improvement

New Feature

Release Notes - Activiti - Version 5.13

Highlights

Bug fixes and various smaller improvements

Check out the Release notes for more details

Sub-task

Bug

Improvement

New Feature

Task

Release Notes - Activiti - Version 5.12.1

Highlights

Important upgrade notes when using script tasks and auto storage of variables

Due to recent changes to the JDK (removing Serializable from sun.org.mozilla.javascript.internal.Undefined), the auto storing of variables is not possible anymore with the built-in Javascript scriping engine. See this link for more information. Each script variable that needs to be stored as process variable needs to be explicitely stored by calling execution.setVariable("variableName", variableValue).

For backwards compatibility reasons, the old behavior can still be used by setting the autoStoreVariables property on a scriptTask to true. As written in the linked articale from above, this might not work when using a recent JDK version and the built-in Javascript scripting engine.

Release Notes - Activiti - Version 5.12

Highlights

Important upgrade note

The internal org.activiti.engine.impl.bpmn.parser.BpmnParseListener interface and related classes have been removed.

Yes, we know many people relied on its capabilities, although it was a class in an internal package. But do not worry: we have introduced a replacement in the api package that offers similar (and even more powerful) functionality. The code is not backwards compatible, but the required changes should be minimal (eg the XML element is replaced by a Java pojo representation of the element). Read more about it in the new 'Advanced' chapter of the userguide.

Bug fixes and various smaller improvements

Check out the Release notes for more details

Sub-task

Bug

Improvement

New Feature

Task

Wish

Release Notes - Activiti - Version 5.11

Highlights

Important upgrade note

In 5.11 we introduce a new history table for process variables. There is an optional migration database script that you can run to generate historic variables for existing process instances. This is optional because the engine will just create those records upon update of the variable if they don't exist.

The files can be found in the database directory of the Activiti distribution org/activiti/db/upgrade/optional.

API Change

The functionality of the repositoryService.suspendProcessDefinitionByXXX has been slightly altered. Previously, calling this method would stop the execution of jobs related to this process definition. Now, calling this method will not do this, but rather make sure a process instance cannot be created from this process definition. We've added a new method with an additional parameter 'suspendProcessInstances' which can be used to get the same behavior: when set to 'true', all the associated process instances will be suspended. This will avoid process instance continuation, including the execution of jobs related to the process instance.

Bug fixes and various smaller improvements

Check out the Release notes for more details

Sub-task

Bug

Improvement

New Feature

Task

Release Notes - Activiti - Version 5.10

Highlights

Bug

Improvement

New Feature

Task

Wish

Release Notes - Activiti - Version 5.9

Highlights

Bug

Improvement

New Feature

Task

Release Notes - Activiti - Version 5.8

Highlights

Bug

Improvement

New Feature

Release Notes - Activiti - Version 5.7

Highlights

Important

A couple of add-on applications have spun off from the Activiti download and started life on their own. Activiti Modeler continues as a Google code project called Signavio Core Components. Activiti Cycle now lives on as Camunda Fox. An evolved version of Activiti KickStart will become part of a new Alfresco cloud case management solution.

Activiti Explorer has acquired Activiti Probe for an undisclosed amount :-) The resulting Activiti Explorer has been restyled and includes more dynamic task management features.

The REST services were rewritten with the Restlet framework with backwards compatibility, so the REST interfaces haven't changed. The previous versions of Activiti included a REST services web application that used the Spring Surf and Webscripts framework. To implement a new or revised REST service you had to learn these frameworks. With moving to Restlet implementing new or revised REST services has become really simple.

The demo setup has been limited to H2 database only, as many people struggled with getting the demo setup to run on their databases. The demo setup is a quick way to get familiar with Activiti and its tools, but it is by no means meant for production purposes. A section 'Changing the database' has been added to the userguide and is intended for advanced users who want to run the Activiti tools on their servers and databases.

Sub-task

Bug

Improvement

New Feature

Task

Release Notes - Activiti - Version 5.6

Highlights

Known upgrade limitation

In the DB schema creation scripts, we've enlarged the max size of certain varchar columns from 255 to 4000. See ACT-236. These schema updates are not part of the automatic upgrade procedure.

Max length of following columns has been set to 4000:

If you want to perform these changes, you can do that manually. Check your database capabilities for the easiest way on changing the type of columns from varchar(255) to varchar(4000). As a fall back, for each table affected, you can:

  1. create a new temporary table
  2. copy the contents from the original to the temporary table
  3. delete the original table
  4. recreate the original table using the new create script with the proper lengths
  5. copy the contents from the temporary table back to the new original table
  6. drop the temporary table

Bug

Improvement

New Feature

Task

Release Notes - Activiti - Version 5.5

Highlights

Bug

Improvement

New Feature

Task

Test

Release Notes - Activiti - Version 5.4

Compatibility note

After releasing 5.3, we discovered that execution listeners and task listeners and expressions were still in non-public api. Those classes were in subpackages of org.activiti.engine.impl..., which has impl in it). org.activiti.engine.impl.pvm.delegate.ExecutionListener, org.activiti.engine.impl.pvm.delegate.TaskListener and org.activiti.engine.impl.pvm.el.Expression have been deprecated. From now on, you should use org.activiti.engine.delegate.ExecutionListener, org.activiti.engine.delegate.TaskListener and org.activiti.engine.delegate.Expression. In the new publicly available API, access to ExecutionListenerExecution.getEventSource() has been removed. Apart from the deprecation compiler warning, the existing code should run fine. But consider switching to the new public API interfaces (without .impl. in the package name).

Highlights

Sub-task

Bug

Improvement

New Feature

Task

Release Notes - Activiti - Version 5.3

Highlights

Bug

Improvement

New Feature

Task

Release Notes - Activiti - Version 5.2

Highlights

Sub-task

Bug

Improvement

New Feature

Task

Wish

Release Notes - Activiti - Version 5.1

Warning

The automatic upgrade does not have enough coverage to have full confidence. For more info, see the user guide, section Database upgrade.

Changes

Highlights

Sub-task

Bug

Improvement

New Feature

Task

Release Notes - Activiti - Version 5.0

Highlights

Bug

Improvement

New Feature

Task

5.0.rc1 (November 1, 2010)

Highlights

Known limitations

Sub-tasks

Bug

Improvement

New Feature

Task

Test

5.0.beta2 (October 1, 2010)

Highlights

Bug

Improvement

New Feature

Task

5.0.beta1 (September 1, 2010)

Known limitations

New Features

Bugs

Improvements

Tasks

5.0.alpha4 (August 1, 2010)

Improvements

New features

Bugfixes

5.0.alpha3 (July 1, 2010)

Improvements

5.0.alpha2 (June 1, 2010)

Improvements

Known limitations

5.0.alpha1 (May 17, 2010)

Known limitations