Skip to content
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.

Releases: Activiti/activiti-modeling-app

7.9.0

03 Mar 13:25
@erdemedeiros erdemedeiros
7.9.0
ef6f137
Compare
Choose a tag to compare
7.9.0 Latest
Latest

Full Changelog: 7.8.0...7.9.0

Assets 2
Loading

7.8.0

24 Jan 16:34
@erdemedeiros erdemedeiros
7.8.0
8cb8ad3
Compare
Choose a tag to compare
7.8.0 
Release version 7.8.0
Assets 2
Loading

7.7.0

16 Dec 10:37
@erdemedeiros erdemedeiros
7.7.0
f8a6589
Compare
Choose a tag to compare
7.7.0

Full Changelog: 7.6.1...7.7.0

Assets 2
Loading

7.6.1

16 Dec 10:21
@erdemedeiros erdemedeiros
7.6.1
d8231f7
Compare
Choose a tag to compare
7.6.1

Full Changelog: 7.6.0...7.6.1

Assets 2
Loading

7.3.0

10 May 14:09
@erdemedeiros erdemedeiros
7.3.0
0e90dc7
Compare
Choose a tag to compare
7.3.0

https://activiti.gitbook.io/activiti-7-developers-guide/releases/7.3.0

Assets 2
Loading

7.2.0

31 Mar 08:07
@erdemedeiros erdemedeiros
7.2.0
0c945f9
Compare
Choose a tag to compare
7.2.0

https://activiti.gitbook.io/activiti-7-developers-guide/releases/7.2.0

Assets 2
Loading

7.1.0-M16

23 Nov 17:44
@gicappa gicappa
7.1.0-M16
9961d59
Compare
Choose a tag to compare
7.1.0-M16

description: Release 7.1.0-M16

7.1.0-M16

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-M16</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-M16</version>
        <scope>import</scope>
        <type>pom</type>
      </dependency>
    </dependencies>
  </dependencyManagement>

In the milestone 7.1.0-M16 you will find the following main fixes & features:

For the complete list of new features and bug fixes, please refer to https://github.com/Activiti/Activiti/milestone/40?closed=1.

Changes from previous milestones

  • Added support ability to configure all message topics destinations used by AAE applications.
    This PR provides configurations to customize destination names for static, i.e. engineEvents and dynamic destinations used by cloud connectors.

Given the following channel binding properties in the application environment context:

spring.cloud.stream.bindings.auditProducer.destination=engineEvents
spring.cloud.stream.bindings.auditConsumer.destination=engineEvents
spring.cloud.stream.bindings.queryConsumer.destination=engineEvents

When the following configuration property is also present in the application environment context:

# to override engineEvents destination name
activiti.cloud.messaging.destinations.engineEvents.name=engine-events

Then the result destination for all three bindings with matching engineEvents key will be configured to

spring.cloud.stream.bindings.auditProducer.destination=engine-events
spring.cloud.stream.bindings.auditConsumer.destination=engine-events
spring.cloud.stream.bindings.queryConsumer.destination=engine-events
  • All destinations support prefix configuration. Destination prefix can be configured using activiti.cloud.messaging.destination-prefix property.

Given the following channel binding properties in the application environment context:

spring.cloud.stream.bindings.auditProducer.destination=engineEvents
spring.cloud.stream.bindings.auditConsumer.destination=engineEvents
spring.cloud.stream.bindings.queryConsumer.destination=engineEvents

When the following configuration property is also present in the application environment context:

# to set the prefix and separator
activiti.cloud.messaging.destination-prefix=namespace

Then the result destination for all three bindings with matching engineEvents key will be configured to

spring.cloud.stream.bindings.auditProducer.destination=namespace_engineEvents
spring.cloud.stream.bindings.auditConsumer.destination=namespace_engineEvents
spring.cloud.stream.bindings.queryConsumer.destination=namespace_engineEvents
  • Destinations support destination separator configuration. Destination separator can be configured using activiti.cloud.messaging.destination-separator property.

Given the following channel binding properties in the application environment context:

# to set the prefix
activiti.cloud.messaging.destination-prefix=namespace

spring.cloud.stream.bindings.auditProducer.destination=engineEvents
spring.cloud.stream.bindings.auditConsumer.destination=engineEvents
spring.cloud.stream.bindings.queryConsumer.destination=engineEvents

When the following configuration property is also present in the application environment context:

# to set the separator
activiti.cloud.messaging.destination-separator=.

Then the result destination for all three bindings with matching engineEvents key will be configured to

spring.cloud.stream.bindings.auditProducer.destination=namespace.engineEvents
spring.cloud.stream.bindings.auditConsumer.destination=namespace.engineEvents
spring.cloud.stream.bindings.queryConsumer.destination=namespace.engineEvents
  • Destination names can be customized via messaging configuration properties to use lower case via transformer configuration properties.

Given the following channel binding properties in the application environment context:

spring.cloud.stream.bindings.auditProducer.destination=engineEvents
spring.cloud.stream.bindings.auditConsumer.destination=engineEvents
spring.cloud.stream.bindings.queryConsumer.destination=engineEvents

When the following configuration property is also present in the application environment context:

# to transform to lower case
activiti.cloud.messaging.destination-transformers-enabled=true
activiti.cloud.messaging.destination-transformers=toLowerCase

Then the result destination for all three bindings with matching engineEvents key will be configured to

spring.cloud.stream.bindings.auditProducer.destination=engineevents
spring.cloud.stream.bindings.auditConsumer.destination=engineevents
spring.cloud.stream.bindings.queryConsumer.destination=engineevents
  • The following configuration properties are introduced to configure Activiti messaging destination properties. The Activiti messaging destinations configuration uses channel destinations as key to configure binding service properties during application context initialization. The effective channel destinations will be configured at runtime by BindingServiceProperties bean post processors.
# Set destination separator to use to build full destinations, i.e. prefix_destination. Default is _
activiti.cloud.messaging.destination-separator

# Set destination prefix to use to build destinations, i.e. prefix_destination. Default is empty string.
activiti.cloud.messaging.destination-prefix

# Enable destination name transformers to apply conversion to all destination name for producers, consumers     
activiti.cloud.messaging.destination-transformers-enabled

# Configure comma-delimited list of destination transformers functions to apply conversion to all destination name for producers, consumers     
activiti.cloud.messaging.destination-transformers

# Configure regex expression to use for replacement of illegal characters in the destination names. Default is [\\t\\s*#:]
activiti.cloud.messaging.destination-illegal-chars-regex

# Configure replacement character for illegal characters in the destination names. Default is -
activiti.cloud.messaging.destination-illegal-chars-replacement

# Configure destination properties to apply customization to producers and consumer channel bindings with matching destination key.
# Destination name to apply for matching channel binding destinations. If empty the key is used as name. Default is empty string.
activiti.cloud.messaging.destinations.[channelBindingDestination].name

# Destination scope to add to destination name, i.e. name.scope. Default is null
activiti.cloud.messaging.destinations.[channelBindingDestination].scope

# Destination prefix to override common destination prefix. Default is null
activiti.cloud.messaging.destinations.[channelBindingDestination].prefix

# Destination separator to override common destination separator. Default is null
activiti.cloud.messaging.destinations.[channelBindingDestination].separator
  • The default property source uses classpath:config/activiti-cloud-messaging.properties with the following default values for backward compatibility with existing destinations:
activiti.cloud.messaging.destination-separator=${ACT_MESSAGING_DEST_SEPARATOR:_}
activiti.cloud.messaging.destination-prefix=${ACT_MESSAGING_DEST_PREFIX:}
activiti.cloud.messaging.destination-transformers-enabled=${ACT_MESSAGING_DEST_TRANSFORMERS_ENABLED:false}
activiti.cloud.messaging.destination-transformers=${ACT_MESSAGING_DEST_TRANSFORMERS:toLowerCase,escapeIllegalChars}

# Default destination scope mappings for cloud stream bindings with matching channel destination
activiti.cloud.messaging.destinations.engineEvents.name=${ACT_RB_ENG_EVT_DEST:engineEvents}
activiti.cloud.messaging.destinations.signalEvent.name=${ACT_RB_SIG_EVT_DEST:signalEvent}
activiti.cloud.messaging.destinations.commandConsumer.name=${ACT_RB_CMD_CONSUMER_DEST:commandConsumer}
activiti.cloud.messaging.destinations.commandConsumer.scope=${activiti.cloud.application.name}
activiti.cloud.messaging.destinations.asyncExecutorJobs.name=${ACT_RB_ASYNC_JOB_EXEC_DEST...
Read more
Assets 2
Loading

7.1.0-M15

08 Oct 13:56
@erdemedeiros erdemedeiros
7.1.0-M15
8c751b6
This commit was signed with the committer’s verified signature.
popovicsandras Popovics András
GPG key ID: A9207E115C2FFA72
Learn about vigilant mode.
Compare
Choose a tag to compare
7.1.0-M15

description: Release 7.1.0-M15

7.1.0-M15

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-M15</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-M15</version>
        <scope>import</scope>
        <type>pom</type>
      </dependency>
    </dependencies>
  </dependencyManagement>

In the milestone 7.1.0-M15 you will find the following main fixes & features:

Changes from previous milestones

  • Enhance Kafka Deployment Strategy by enabling dynamic scaling of the query consumer PODs: previously, while using partioned message streams, the property partitionCount was used to define at the same time the number of partitions and the number of replicas for query service for both RabbitMQ and Kafka binders. However, Kafka binder supports dynamically scaling and one replica can handle more than one partition. Starting from version 7.1.0-M15 the number of partitions and the number of replica for query service are set independently while using Kafka binder: partitionCount is used to define the number of partions and replicaCount is used to define the number of replicas for query service.partitionCount should be greater than or equals to replicaCount.
global:
  messaging:
    broker: kafka
    partitioned: true
    # global.messaging.partitionCount -- set the Kafka partition number
    partitionCount: 4
activiti-cloud-query:
  # replicaCount -- set the Kafka consumer number
  replicaCount: 2
  • Use client/secret auth for Keycloak Admin Client: previously, in order to retrieve users and groups from Keycloak, Activiti Cloud used to connect using the credentials (username/password) of a special user called client that was added to the Realm. Starting from the version 7.1.0-M15 the user client was removed in favor of a new keycloak client called (activiti-keycloak). As consenquence:
    • The following mandatory properties has been added:
      • activiti.keycloak.client-id=${ACT_KEYCLOAK_CLIENT_ID:activiti-keycloak}
      • activiti.keycloak.client-secret=${ACT_KEYCLOAK_CLIENT_SECRET:}
    • The following properties has been removed:
      • activiti.keycloak.admin-client-app=${ACT_KEYCLOAK_CLIENT_APP:admin-cli}
      • activiti.keycloak.client-user=${ACT_KEYCLOAK_CLIENT_USER:client}
      • activiti.keycloak.client-password=${ACT_KEYCLOAK_CLIENT_PASSWORD:client}

Configuration with Helm charts:

It's possible to create a default Activiti Keycloak Client Kubernetes secret with Helm by using the following values (replace changeit by the secret of your choice):

global:
  keycloak:
    clientSecret: changeit

Or, if you prefer, you can use existing Activiti Keycloak Client Kubernetes secret by enablinguseExistingClientSecret:

kubectl create secret generic activiti-keycloak-client \
   --from-literal=clientId=activiti-keycloak \
   --from-literal=clientSecret=changeit

global:
  keycloak:
    clientSecretName: activiti-keycloak-client
    useExistingClientSecret: true

Under the hood, the deployment will add the following environment variables to container specs:

specs:
  containers:
    - name: runtime-bundle
      env:
        - name: ACTIVITI_KEYCLOAK_CLIENT_ID
          valueFrom:
            secretKeyRef:
              key: clientId
              name: activiti-keycloak-secret
        - name: ACTIVITI_KEYCLOAK_CLIENT_SECRET
          valueFrom:
            secretKeyRef:
              key: clientSecret
              name: activiti-keycloak-secret

  • Removal of activiti-cloud-services-common-identity-keycloak from connector starter: activiti-cloud-starter-connector is no longer bringing the depencency toactiviti-cloud-services-common-identity-keycloak, please add it explicitly in the case where your connector implementation was rellying on it.

  • Improve message event handling when there are several runtime bundles: by default, binding destinations related to BPMN Messages are now scoped by Activiti Cloud Application. This allow having more than one Runtime Bundle using the same message broker. This change should be transparent for most of the users, but here are the changes performed:

    New default values starting from version 7.1.0-m15:

spring.cloud.stream.bindings.input.destination=messageEvents${activiti.cloud.messaging.destination-separator}${activiti.cloud.application.name}
spring.cloud.stream.bindings.output.destination=commandConsumer${activiti.cloud.messaging.destination-separator}${activiti.cloud.application.name}
spring.cloud.stream.bindings.commandConsumer.destination=${ACT_RB_COMMAND_CONSUMER_DEST:commandConsumer${activiti.cloud.messaging.destination-separator}${activiti.cloud.application.name}}
spring.cloud.stream.bindings.commandResults.destination=${ACT_RB_COMMAND_RESULTS_DEST:commandResults${activiti.cloud.messaging.destination-separator}${activiti.cloud.application.name}}
spring.cloud.stream.bindings.messageEvents.destination=messageEvents${activiti.cloud.messaging.destination-separator}${activiti.cloud.application.name}

Previous default values:

spring.cloud.stream.bindings.input.destination=messageEvents
spring.cloud.stream.bindings.output.destination=commandConsumer
spring.cloud.stream.bindings.commandConsumer.destination=commandConsumer
spring.cloud.stream.bindings.commandResults.destination=commandResults
spring.cloud.stream.bindings.messageEvents.destination=messageEvents
Assets 2
Loading