7.1.0-M7
7.1.0-M7
You can consume all the Activiti artifacts for this release from Alfresco Nexus:
1
<repositories>
2
<repository>
3
<id>activiti-releases</id>
4
<url>https://artifacts.alfresco.com/nexus/content/repositories/activiti-releases</url>
5
</repository>
6
</repositories>
Copied!
Activiti Cloud:
1
<dependencyManagement>
2
<dependencies>
3
<dependency>
4
<groupId>org.activiti.cloud</groupId>
5
<artifactId>activiti-cloud-dependencies</artifactId>
6
<version>7.1.0-M7</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</groupId>
5
<artifactId>activiti-dependencies</artifactId>
6
<version>7.1.0-M7</version>
7
<scope>import</scope>
8
<type>pom</type>
9
</dependency>
10
</dependencies>
11
</dependencyManagement>
Copied!
- **Error handling for cloud connectors: **see the section Error handling for Cloud Connectors more details.
- Possibility do explicitly define the variable type while starting a process via REST API. The variables should be provided in the format
key/valuewherekeyis going to be the variable name andvaluecan be either directly the actual value (in which case Activiti will try to guess the type) or a complex object having two fields:valuewith the string representation of the value andtypeexplicitly defining the type. The example below uses a mix of these two options:
1
"variables":{
2
"dateValue":{
3
"type":"date",
4
"value":"1970-01-01T01:01:01.001Z"
5
},
6
"date": "1970-01-01T01:01:01.001Z",
7
"stringValue":{
8
"type":"string",
9
"value":"name"
10
},
11
"string":"name",
12
"bigDecimalValue":{
13
"type":"BigDecimal",
14
"value":"10.00"
15
},
16
"intValue":{
17
"type":"integer",
18
"value":"10"
19
},
20
"int":10
21
"booleanValue":{
22
"type":"boolean",
23
"value":"true"
24
},
25
"boolean":true,
26
"doubleValue":{
27
"type":"double",
28
"value":"10.00"
29
}
30
"double":10.0
31
}
Copied!
- Improve information provided by
PROCESS_CANCELLED_EVENT - Fix support of
${initiator}expression. - Provide candidates info when fetching a task by ID.
- Update to Spring Boot
2.1.13.RELEASE.
Known issues / Changes from previous milestones
jaxb-apidependency at the engine level: the dependency tojaxb-apiwas added directly at the engine level, so this extra dependency doesn't need to be declared along side withactiviti-cloud-starter-runtime-bundle, as in the previous milestones.- Maven artifacts refactoring: the number of different
groupIdsproduced byActivitiandActiviti Cloudhas been reduced to only two (org.activitiandorg.activiti.cloud). This is a breaking change compared with previous milestones:org.activiti.cloud.<suffix>will becomeorg.activiti.cloudandorg.activiti.<suffix>will becomeorg.activiti. - Fix semantic versioning: use
-character instead of.:7.1.0-M7and not7.1.0.M7. - Milestone artifacts are no longer published to Maven Central: so far, milestone artifacts are going to be published to Alfresco Nexus.
1
<repositories>
2
<repository>
3
<id>activiti-releases</id>
4
<url>https://artifacts.alfresco.com/nexus/content/repositories/activiti-releases</url>
5
</repository>
6
</repositories>
Copied!
- Java 8 support has been dropped
- **Git repositories restructuring: **carrying on the work started in the previous milestone, several git repositories were merged together and so far Activiti projects use only five main repositories:
- ​activiti-cloud-application: holds Activiti Cloud BoM file (
org.activiti.cloud:activiti-cloud-dependencies) and example Spring Boot applications used to generate example Docker images.
Last modified 2d ago