---
description: 7.1.0.M3.1
---

# 7.1.0 M3

You can consume all the Activiti artifacts for this release from Maven Central:

_Activiti Cloud:_

```markup
<dependencyManagement>
   <dependencies>
     <dependency>
       <groupId>org.activiti.cloud.dependencies</groupId>
       <artifactId>activiti-cloud-dependencies</artifactId>
       <version>7.1.0.M3.1</version>
       <scope>import</scope>
       <type>pom</type>
     </dependency>
   </dependencies>
 </dependencyManagement>
```

_Activiti Core_

```markup
<dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>org.activiti.dependencies</groupId>
        <artifactId>activiti-dependencies</artifactId>
        <version>7.1.0.M3.1</version>
        <scope>import</scope>
        <type>pom</type>
      </dependency>
    </dependencies>
  </dependencyManagement>
```

In the 7.1.0.M3.1 release you will find the following [main fixes & features](https://github.com/Activiti/Activiti/milestone/21?closed=1):

* New common variable mapping logic for connectors, user tasks and call activities.
* Constant values are not part of mappings anymore. They have their own specific field in the `extensions.json` .
* BPMN elements:
  * Support of Timers (start, intermediate catch, boundary)\*\* \*\*and Inclusive Gateways in the Activiti Modeling Application
  * Enhancement of Timers and async tasks execution for Activiti Cloud: jobs are now relying on message broker to distribute the load between the different replicas of the runtime bundle.

You can also deploy our Example HELM charts using your favorite cloud platform (i.e. AWS, GCP, Azure...) or on-premise Kubernetes installation by following our [Getting Started Guide](https://activiti.gitbook.io/activiti-7-developers-guide/getting-started/getting-started-activiti-cloud)

### Known issues / Changes from 7.0.x

**Variable mapping**

The new variable mapping logic comes with newly defined edge cases, where no mapping means that all the variables are gonna be mapped, with same names, to the element whose mapping is missing:

```
"mapping": {}
```

�And existing but empty mapping means that no variables are gonna be mapped to the element with id `taskId`:

```
"mapping": { 
    "taskId":{ 
        "inputs": {}, 
        "outputs"t:{} 
    } 
}
```

�If the usual mapping is found for a task inside the process extension file, only the variables that are mapped will be available to the task.

�Constant values specified in their own field in the `extensions.json` file associated to a process definition.\
\
&#xNAN;_&#x42;efore 7.1.0.M3.1:_

```
"mappings": {
    "taskId": {
        "inputs": {
            “_constant_value_": {
                "type": "static_value",
                "value": "myConstantValue"
            }
        }
    }
}
```

_�From 7.1.0.M3.1:_

```
"mappings": {},
"constants" : {
    "taskId": {
        "_constant_value_" : {
          "value": "myConstantValue"
        }
    }
}
```

**Async executor**

Async executor is now enable by default. It can be disabled by setting the property `spring.activiti.async-executor-activate` to `false`. However async executor should be active to handle timer events and tasks marked as asynchronous.

**Call activity XML extensions**

Support for variables mapping from/to call activity to/from called process has ben removed from XML (`activiti:in`, `activiti:out`) in benefit of variables mapping defined in extensions file.
