7.1.0-M9

Activiti & Activiti Cloud Developers Guide
Search…
7.1.0-M9
Release 7.1.0-M9
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-M9</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-M9</version>
7
        <scope>import</scope>
8
        <type>pom</type>
9
      </dependency>
10
    </dependencies>
11
  </dependencyManagement>
Copied!
In the 7.1.0-M9 release you will find the following main fixes & features:
Mark audit producer channel as transactional (messages sent from the runtime bundle to query and audit services): If Activiti successfully commits its transaction, the producer binder will also execute commit on the transacted channel to publish messages. In the event Activiti database transaction is rolled back, the producer binder will rollback any messages waiting for commit in the output stream channel. In case of an infrastructure issue where messages cannot be sent, the producer send()method will return false and will raise an exception to signal the Activiti closing manager to rollback the database transaction.
Allow multi-instance Result Collection (loopDataOutputRef) to collect all the local variables:
when both loopDataOutputRef and outputDataItem (Result element) are set in the xml file, only the value of the variable specified in outputDataItem will be collected in loopDataOutputRef. The result will be a list of values. I.e.
1
          <multiInstanceLoopCharacteristics isSequential="false">
2
            <loopCardinality>2</loopCardinality>
3
            <loopDataOutputRef>meals</loopDataOutputRef>
4
            <outputDataItem name="meal"/>
5
          </multiInstanceLoopCharacteristics>
Copied!
Example of result: ["pizza", "pasta"]
when only loopDataOutputRef is set, all the local variables will be collected in loopDataOutputRef. The result will be a list of maps.
1
          <multiInstanceLoopCharacteristics isSequential="false">
2
            <loopCardinality>2</loopCardinality>
3
            <loopDataOutputRef>result</loopDataOutputRef>
4
          </multiInstanceLoopCharacteristics>
Copied!
Example of result: [{"meal": "pizza", "anotherLocalVariable": "value1"}, {"meal": "pasta", "anotherLocalVariable": "value2"}]
[Modeling Application] Add support for expressions on the called element of a Call Activity.
Fix AsyncJobAddedNotification.closed that was called inside the transaction.
Fix exception when a variable of type LocalDateTime is created
7.1.0-M10
7.1.0-M8
Last modified 5mo ago
Copy link
Contents
In the 7.1.0-M9 release you will find the following main fixes & features: