7.1.0-M16

Activiti & Activiti Cloud Developers Guide
Search…
7.1.0-M16
Release 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:
​Support the ability to configure topics on shared message broker instance: Add the possibility to customize destination names used by Activiti Cloud. See the next section for more details.
​Update Helm charts to use readiness and liveness probes for health checks.
​Configure Swagger UI to use implicit flow auth: authentication was integrated into the Swagger UI so that now it's possible to call the APIs directly from the Swagger UI
​
​
​Allow expressions in-process variables​
​Allow expressions in-process extension variables​
​Migrate from Swagger2 to OAS3​
​Add custom JUEL functions to resolve current date and current date+time​
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:asyncExecutorJobs}
activiti.cloud.messaging.destinations.asyncExecutorJobs.scope=${activiti.cloud.application.name}
activiti.cloud.messaging.destinations.messageEvents.name=${ACT_RB_MSG_EVT_DEST:messageEvents}
activiti.cloud.messaging.destinations.messageEvents.scope=${activiti.cloud.application.name}
activiti.cloud.messaging.destinations.commandResults.name=${ACT_RB_CMD_RES_DEST:commandResults}
activiti.cloud.messaging.destinations.commandResults.scope=${activiti.cloud.application.name}
activiti.cloud.messaging.destinations.integrationResult.name=${ACT_INT_RES_CONSUMER:integrationResult}
activiti.cloud.messaging.destinations.integrationResult.scope=${spring.application.name}
activiti.cloud.messaging.destinations.integrationError.name=${ACT_INT_ERR_CONSUMER:integrationError}
activiti.cloud.messaging.destinations.integrationError.scope=${spring.application.name}
It is possible to configure property source in file:config/activiti-cloud-messaging.properties or using standard Spring Boot application.properties file or with provided environment variable shortcuts
Connector Destinations Customization Binding destinations for Service Tasks Cloud Connectors are sourced from Bpmn Model definitions on startup.
Connector Messaging Reply Destinations Customization Connectors use responseDestination and errorDestination attributes in IntegrationRequest event to send a response back to the integration result consumer. The integration request producer will provide destinations for a response when sending the request.
Message Event Reply Destination Customization Message events will now use messageEventRouterDestination message header attribute to route correlated messages back to the command consumer. The message event producer will provide a destination for a response when sending the request.
Enabling destination transformer will apply to lower case transformation filter and replace illegal characters with replacement char for all destinations.
7.1.0-M17
7.1.0-M15
Last modified 8mo ago
Copy link
Outline
In the milestone 7.1.0-M16 you will find the following main fixes & features:
Changes from previous milestones