7.1.0-M10

Release 7.1.0-M10

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

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

  • Expose Service Tasks in query service via REST API:

    • List of all service tasks: GET /admin/v1/service-tasks

    • Get service task by id: GET /admin/v1/service-tasks/{serviceTaskId}

    • List of all service task for process instance: GET /admin/v1/process-instances/{processInstanceId}/service-tasks

    • List of all service tasks filtered by status (i.e. STARTED, COMPLETED, ERROR, CANCELLED):

    GET /admin/v1/service-tasks?status={status}

    • List Sevice Task integration context. It exposes information such as status, error message, error stack trace, error date, etc. GET /admin/v1/service-tasks/{serviceTaksId}/integration-context

  • Extra filtering on REST API for query service.

  • Possibility to include a root cause or a message while sending a CloudBpmnError.

  • Variable mapping representation and behavior changes (see next section).

Known issues / Changes from previous milestones

  • Variable mapping representation behavior changes:

    • The default behavior for mapping variables between processes and tasks has changed. Previously, if a given task was not referenced in the mappings section of the extension file*-extensions.json), Activiti would apply the "Send all" strategy, meaning that all the process variables would be copied to the task level and all the task variables would be copied back to the process level. Starting from this milestone, by default, nothing will happen (no variable will be copied from the process to task and no variable will be copied from the task to the process). If you still want the "Send all" strategy, you need to explicitly define it in the mappings section, by setting the new attribute mappingType to MAP_ALL. Note that nothing will change if you're not using the "Send all" or the "Send none" strategies: regular mapping will keep working as before.

    • Possibility to define different strategies for input or output mappings by setting the mappingType to:

      • MAP_ALL: will use the "Send all" strategy for both input and output mappings.

      • MAP_ALL_INPUTS: will use the "Send all" strategy for input mapping and regular mapping for output mapping.

      • MAP_ALL_OUTPUTS: will use the "Send all" strategy for output mapping and regular mapping for input mapping.

Example of "Send all" mapping:

"mappings": {
"task_id": {
"mappingType": "MAP_ALL"
}
}

Example of different strategies for input and output mappings (regular mapping for inputs and "Send all" for outputs):

"mappings": {
"task_id": {
"mappingType": "MAP_ALL_OUTPUTS",
"inputs": {
"clientName": {
"type": "variable",
"value": "firstName"
}
}
}
}