Skip navigation
All Places > Alfresco Process Services & Activiti (BPM) > Blog > 2018 > January

30 weeks in and we are making huge progress in our Cloud Native approach. We are closing January and we will be working in polishing some rough edges in our main components (Runtime Bundle, Query/Notifications and Audit)  and starting some PoCs on the new stuff that we want to get before doing a major release. This is an excellent opportunity to join the community, if you are interested in helping out or working on your own extension get in touch!



@daisuke-yoshimoto started the Investigation for that signals are exchanged cross multiple Runtime Bundles(each database).

@constantin-ciobotaru Investigated options to add Kubernetes ConfigMaps and Secrets and integration with spring-cloud-incubator/spring-cloud-kubernetes.

@mteodori Started to update the cloud example UI to Angular/ADF.

@lucianoprea started investigating #1688 and updated the copyright for all Activiti github repos

@ffazzini solved the performance problem of keeping the whole activiti and the dbp working increasing the ec2 instances size, started a poc on bdd tests for activiti

@ryandawsonuk Started a PoC on separating the GraphQL query and notification components to run in different containers and in developing this came to decide that the approach of the PoC was not the best direction. Reviewed pull requests and helped with the work to move to dedicated channels for connectors, identifying what appears to be a bug in the latest spring cloud sleuth.

@erdemedeiros Kept working to move connectors to dedicated channels (, Even if this approach requires some extra configuration at connectors side, it was confirmed by Spring Cloud Stream guys as being the direction to go. Currently creating a reproducer for a problem related to trace IDs (Sleuth) when using dynamically bound destinations.

@salaboy Working on the initial PoC for the Application Services which will deploy Activiti Cloud Applications and will serve as the entry point for users and UIs which wants to interact with them. We are using Spring Cloud Deployers so we are collaborating with their community to get a generic mechanism for Activiti Cloud Apps provisioning. 


As usual:

Ping us in Gitter if you want to contribute:

If you want to get started with Activiti Cloud visit our Gitbook:

Last week the team presented Activiti Cloud at DevCon in Lisbon. We missed @erdemedeiros but we met @igdianov  and @daisuke-yoshimoto at DevCon so we manage to do a face-to-face planning sessions and brainstorming about the future of the projects. This week we will be doing heavy planning for our up coming monthly release plus we will be closing up some of the open topics that we had from the last previous months. We are making great progress on our kubernetes deployments, so we are looking forward to get some feedback from the community. At DevCon we introduced our refreshingly new Logo for the Activiti & Activiti Cloud projects and we are working on a new website to host the new projects:

Activiti & Activiti Cloud



@constantin-ciobotaru added back contracts consumer tests and investigated ConfigMaps in Kubernetes

@mteodori attended to DevCon with the Activiti Team.

@lucianoprea investigated a easy way to turn on debug logging in our apps #1678 and looked into an activiti cloud connector developed in another language #1672

@ffazzini finished to integrate activiti in alfresco-dbp anaxes, fixed swagger in audit service

@ryandawsonuk attended DevCon and presented the trending topics Twitter example in the Activiti Cloud Deep Dive session

@erdemedeiros worked on PoCs for changes on connectors integration mechanism (, and Integrated Awaitility library to handle asynchronous tests (

@salaboy presented at DevCon an introduction to the main concepts in Activiti Cloud.

As usual:

Ping us in Gitter if you want to contribute:

If you want to get started with Activiti Cloud visit our Gitbook:

(08/01/18 - 15/01/18) Last week the team released 7-201712-EA - you can read about the 7-201712-EA release at


@constantin-ciobotaru finished modeling service for release and fixed bugs

@mteodori integrated dependency check from develop into 5.x and updated libraries with known vulnerabilities

@lucianoprea worked on making mongo default for Audit #1661, tested the examples after the release and start looking into finding a easy way to turn on debug logging in our apps #1678

@ffazzini continued working on AWS deployment, now having used helm to solve a problem of needing to use the dynamically-assigned AWS url at deploy time

@ryandawsonuk fixed a problem with connector transaction management (#1660), improved the performance of the trending topics twitter example (#1671 ) and managed the release process for 7-201712-EA

@erdemedeiros added the node id (‘id’ attribute fro BPMN file) to Integration Requests and Integration results ( Considered the different possibilities to improve the Integration Results delivery (


Ping us in Gitter if you want to contribute:

If you want to get started with Activiti Cloud visit our Gitbook:

The activiti team is happy to announce that Activiti & Activiti Cloud 7-201712-EA artifacts are out and we encourage people in the community to try them out.


For anybody looking to try out the new Activiti Cloud features in Activiti 7, the best place to start is GitHub - Activiti/activiti-cloud-examples: Activiti Cloud Examples using Docker Images from:…  or the gitbook Activiti 7 & Activiti Cloud Developers Guide · GitBook 


In the 7-201712-EA release we've added improvements to the way cloud connectors manage transactions, which improves their performance. We've added an example based around marketing campaigns for social media content in which you can see how well the connectors perform. The rate of data input and the number of replicas for cloud components in this example can be controlled in the deployment descriptor so that it's easy to play with these variables to test scalability. We'll be talking more about this example at Alfresco DevCon 2018.


We've also added process model and organisation services, which are preparations for future work that will support logical grouping and editing of BPM models/diagrams.


As part of this release we also aligned with Spring Boot 2.0.0.M7 and Spring Cloud Finchley.M5.


You can find our published artifacts in [Maven Central]
and our Docker Images have been tagged so you can use the 7-201712-EA tag for each of our images. You can find more details on
[Activiti in Docker Hub]


Ping us in Gitter if you want to contribute, give feedack, or if you need help reporting an issue:

(01/01/18 - 07/01/18) The team has been focusing on preparing for the next Early Access release and preparing our Trending Topics twitter example to be presented at DevCon. The work has helped us realise some significant improvements in memory profile and demonstrate Activiti Cloud’s scaling capabilities. We’re also working on improving our processes for end to end testing by devoting time to using a fully-featured hosted environment.


@constantin-ciobotaru worked on the integration of the new activiti-cloud-process-model-service and activiti-cloud-org-service to resolve some bugs in the way they interact

@lucianoprea worked on the activiti-cloud-modeling-backend in order to build an application using the activiti-cloud-process-model-service and activiti-cloud-org-service as dependencies and publish a docker image containing that application

@ffazzini created a kubernetes cluster running on alfresco aws, deployed and tested successfully activiti main components

@ryandawsonuk improved the memory profile of the components for the trending topics twitter example and applied this back to the other examples, now enabling us to run more replicas of services and process at a higher rate of tweets when running in minikube

@erdemedeiros updated Spring Boot Maven plugin to version 2.0.0.M7. Review and merging pending PRs. Start adding the flow node id (from the process definition) to the integration requests in order to improve the audit events.


Ping us in Gitter if you want to contribute:


If you want to get started with Activiti Cloud visit our Gitbook:

(25/12/17 - 31/12/17) This week was Christmas and New Year so many of the Activiti team were on holiday. Those of the team who were around used the time to improve our examples of how to use Activiti Cloud and to make plans for areas to improve in the start of the new year. We also tried to keep chipping in to answer questions from the community, especially in the forums.