7.1.0-M13

Activiti & Activiti Cloud Developers Guide
Search…
7.1.0-M13
Release 7.1.0-M13
You can consume all the Activiti artifacts for this release from Alfresco Nexus:
<repositories>
  <repository>
    <id>activiti-releases</id>
    <url>https://artifacts.alfresco.com/nexus/content/repositories/activiti-releases</url>
  </repository>
</repositories>
Activiti Cloud:
<dependencyManagement>
   <dependencies>
     <dependency>
       <groupId>org.activiti.cloud</groupId>
       <artifactId>activiti-cloud-dependencies</artifactId>
       <version>7.1.0-M13</version>
       <scope>import</scope>
       <type>pom</type>
     </dependency>
   </dependencies>
 </dependencyManagement>
Activiti Core
  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>org.activiti</groupId>
        <artifactId>activiti-dependencies</artifactId>
        <version>7.1.0-M13</version>
        <scope>import</scope>
        <type>pom</type>
      </dependency>
    </dependencies>
  </dependencyManagement>
In the milestone 7.1.0-M13 you will find the following main fixes & features:
​Add support for partitioned message streams: messages used to transfer data from the runtime bundle to query and audit service can be partitioned. There will be as many instances of the consumer as the number of partitions. Each instance will consume data from a single partition. In Helm deployment, partitioning can be enabled by providing the following extra values (partitionCount defines how many partitions will be used and the Helm deployment will create that many replicas of query service using a StatefulSet rather than a Deployment):
global:
  messaging:
    # global.messaging.partitioned -- enables partitioned messaging in combination with messaging.enabled=true && messaging.role=producer|consumer
    partitioned: true
    # global.messaging.partitionCount -- configures number of partitioned consumers 
    partitionCount: 2
Result of kubectl get pods:
NAME                                           READY   STATUS    RESTARTS   AGE
m13-activiti-cloud-connector-66bb74576-j42hm   1/1     Running   0          153m
m13-activiti-cloud-modeling-769fcb67b5-kx9qk   1/1     Running   0          153m
m13-activiti-cloud-query-0                     1/1     Running   0          153m
m13-activiti-cloud-query-1                     1/1     Running   0          153m
m13-activiti-modeling-app-847d8dfbb-2lggd      1/1     Running   0          153m
m13-keycloak-0                                 1/1     Running   0          153m
m13-postgresql-0                               1/1     Running   0          153m
m13-postgresql-id-0                            1/1     Running   0          153m
m13-runtime-bundle-7d568d9844-5vhtq            1/1     Running   0          153m
rabbitmq-0                                     1/1     Running   0          153m
​Add Activiti Cloud application support for Kafka binder: in addition to Rabbit MQ binder (that remains the default one), the example docker images generated by activiti-cloud-application are also embedding Kafka binder. In order to use it instead of Rabbit MQ binder, pass the following values during Helm deployment:
global:
  messaging:
    broker: kafka
kafka:
  enabled: true
rabbitmq:
  enabled: false
Result of kubectl get pods:
NAMESPACE   NAME                                                 READY   STATUS    RESTARTS   AGE
m13-kafka   activiti-activiti-cloud-connector-6ff67bc988-s88jj   1/1     Running   0          4h35m
m13-kafka   activiti-activiti-cloud-modeling-98499f5d5-lw9hd     1/1     Running   0          4h35m
m13-kafka   activiti-activiti-cloud-query-fd5bcbc9f-89jrl        1/1     Running   0          4h35m
m13-kafka   activiti-activiti-modeling-app-bbd8d97c8-qnl46       1/1     Running   0          4h18m
m13-kafka   activiti-keycloak-0                                  1/1     Running   0          4h35m
m13-kafka   activiti-postgresql-0                                1/1     Running   0          4h35m
m13-kafka   activiti-postgresql-id-0                             1/1     Running   0          4h35m
m13-kafka   activiti-runtime-bundle-865895df8d-hhgwm             1/1     Running   0          4h35m
m13-kafka   kafka-0                                              1/1     Running   0          4h35m
m13-kafka   zookeeper-0                                          1/1     Running   0          4h35m
Kafka or Rabbitmq message brokers can be deployed conditionally as part of Helm release using rabbitmq.enabled or kafka.enabled. The default values for Kafka and Rabbitmq have been set up to use message brokers provided with the Helm chart. It is possible to disable message broker deployments and use external Kafka or Rabbitmq by overriding global.kafka or global.rabbitmq values, i.e. global.kafka.brokers (Multiple brokers can be provided in a comma-separated list, e.g. host1:port1,host2:port2),global.kafka.zkNodes (External Zookeeper nodes).
​Improve common helm charts for upgrades with customizations​
​Block reflection on JUEL Expressions​
​Upgrade to Spring Boot 2.4.5 and Spring Cloud 2020.0.2​
Fix Modeling-Service Schemas Problem​
Fix ProcessDefinitionName not provided for sub-processes​
Fix Error color state diagram is not displayed​
Fix Intermittent Sleuth failures on GraphQL service​
Fix Audit service fails with Oracle DB​
Fix M12 version run program prompting circular reference problem​
Changes from previous milestones
​The use of reflection is no longer allowed inside JUEL expressions​
7.1.0-M14
7.1.0-M12
Last modified 8mo ago
Copy link
Outline
In the milestone 7.1.0-M13 you will find the following main fixes & features:
Changes from previous milestones