7.1.0 M5
7.1.0.M5
You can consume all the Activiti artifacts for this release from Maven Central:
Activiti Cloud:
1
<dependencyManagement>
2
<dependencies>
3
<dependency>
4
<groupId>org.activiti.cloud.dependencies</groupId>
5
<artifactId>activiti-cloud-dependencies</artifactId>
6
<version>7.1.0.M5</version>
7
<scope>import</scope>
8
<type>pom</type>
9
</dependency>
10
</dependencies>
11
</dependencyManagement>
Copied!
Activiti Core
1
<dependencyManagement>
2
<dependencies>
3
<dependency>
4
<groupId>org.activiti.dependencies</groupId>
5
<artifactId>activiti-dependencies</artifactId>
6
<version>7.1.0.M5</version>
7
<scope>import</scope>
8
<type>pom</type>
9
</dependency>
10
</dependencies>
11
</dependencyManagement>
Copied!
- BPMN elements
- Add support for multi-instances
- Cloud Native Bpmn Message Events Support: It includes support for BPMN throw message event. See description of pull request #416 for more details. In this first iteration message store backend is in memory only and it's not ready for production. The next iteration will bring alternatives for persistent message store backends. It's available thanks to new spring boot starter:
1
<dependency>
2
<groupId>org.activiti.cloud.rb</groupId>
3
<artifactId>activiti-cloud-starter-message-connector</artifactId>
4
</dependency>
Copied!
- Add support for expression on input variable mapping: now it's possible to reference process variables inside an input variable mapping. I.e.":
1
{
2
"inputs": {
3
"input-json-template": {
4
"type": "value",
5
"value": {
6
"name": "${name}",
7
"age": "${age}",
8
"resident": "${resident}"
9
}
10
}
11
}
12
}
Copied!
${name}, ${age} and ${resident} will be replaced by the related process variable values before calling the connector.- Upgrade Spring Boot and Spring cloud versions:
- Spring boot: 2.1.10.RELEASE
- Spring cloud: Greenwich.SR3
- Removal of
ComponentScanonorg.activiti: in the previous versions Activiti Core andActiviti Cloudwere relying onComponentScanannotation on the packageorg.activiti. This was causing several issues and misbehaviours. In version7.1.0.M6a big work was carried on this level to make sure that we rely on auto configurations only.
Known issues / Changes from 7.0.x
Add Liquibase to Org service (modeling back end)
Liquibase will handle database initialisation and schema migration on Org service (modeling back end).
Known issues
Last modified 2d ago