7.1.0-M7

7.1.0-M7

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

In the 7.1.0-M7 release you will find the following main fixes & features:

  • **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/value where key is going to be the variable name and value can be either directly the actual value (in which case Activiti will try to guess the type) or a complex object having two fields: value with the string representation of the value and type explicitly defining the type. The example below uses a mix of these two options:

"variables":{
      "dateValue":{
         "type":"date",
         "value":"1970-01-01T01:01:01.001Z"
      },
      "date": "1970-01-01T01:01:01.001Z",
      "stringValue":{
         "type":"string",
         "value":"name"
      },
      "string":"name",
      "bigDecimalValue":{
         "type":"BigDecimal",
         "value":"10.00"
      },
      "intValue":{
         "type":"integer",
         "value":"10"
      },
      "int":10
      "booleanValue":{
         "type":"boolean",
         "value":"true"
      },
      "boolean":true,
      "doubleValue":{
         "type":"double",
         "value":"10.00"
      }
      "double":10.0
   }

  • 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-api dependency at the engine level: the dependency to jaxb-api was added directly at the engine level, so this extra dependency doesn't need to be declared along side with activiti-cloud-starter-runtime-bundle, as in the previous milestones.

  • Maven artifacts refactoring: the number of different groupIds produced by Activiti and Activiti Cloud has been reduced to only two (org.activiti and org.activiti.cloud). This is a breaking change compared with previous milestones: org.activiti.cloud.<suffix> will become org.activiti.cloud and org.activiti.<suffix> will become org.activiti.

  • Fix semantic versioning: use - character instead of .: 7.1.0-M7 and not 7.1.0.M7.

  • Milestone artifacts are no longer published to Maven Central: so far, milestone artifacts are going to be published to Alfresco Nexus.

<repositories>
  <repository>
    <id>activiti-releases</id>
    <url>https://artifacts.alfresco.com/nexus/content/repositories/activiti-releases</url>
  </repository>
</repositories>

  • 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:

Previous7.1.0-M8Next7.1.0.M6

Last updated