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

Last week we made some progress on refining our services to support more scenarios and we included a new Angular 5 application to start building our Demo UI against Activiti Cloud Services. @igdianovprovided support for GraphQL which is now being migrated to the new Angular 5 app. The new App is a great place to get involved with the project and to test the advantage of the new endpoints, APIs and feature. We keep our testing against PKS (Pivotal Container Services) and improving our Trending Topics Campaign BluePrintto support more use cases. 


@diegonayalazo worked on refining the Quickstarts in our GitBook and started working with our acceptance test project to improve our coverage during automation.

@igdianov Integrated GraphQL Query support into Activiti-Cloud-Demo-Ui example using Apollo Client JS libraries:

@daisuke-yoshimoto is working on implementing Signal Throw Event Cloud Behavior that broadcasts signals to all Runtime Bundles by using Spring Cloud Stream.

@constantin-ciobotaru worked for springfox-data-rest-patch and to enable swagger for process-model and organization services, worked for the fix on springfox side, started acceptance tests for modeling service

@mteodori fixed latest Spring and Jackson security vulnerabilities created a ticket for newly discovered Log4J one and moved dependency-check to a profile to make build faster

@lucianoprea created an endpoint to validate BPMN models correctness that should be triggered before saving a new Process Model

@ffazzini automated deployment investigation around performance test solutions

@balsarori Helped with investigating how suspend/activate events work. Started to work on simplifying extendability of ServiceTaskParseHandler on 5.x.

@ryandawsonuk has been adding access control on the REST part of the query module. This has required some refactoring of the access control implementation on the runtime bundle and ensuring that further data is fed through into query.

@erdemedeiros kept working on the PoC to support Alfresco REST APIs guidelines ( Some work still need to be done concerning pagination.

@salaboy worked on improving the Trending Topic Campaings BluePrint ( and started a deeper research on how to use Spring Cloud Kubernetes Config and Registry modules. Also did some research on Kubernetes Service Catalog and how this will related to Spring Cloud Kubernetes.


Check the February milestoneto find the issues that we are currently working on this month and get in touch if you want to contribute:

We are looking forward to mentor people on the technologies that we are using to submit their first Pull Request ;)

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

Last week we focused on planning and making sure that we polish our getting started experience. You will notice that we are refactoring our GitBook and our activiti-cloud-examples repository to reduce the learning curve and the number of steps required to get our infrastructure up and running. We will continue this refinement process with our Trending Topic BluePrint which was moved to a separate GitHub repository now (we will also publish ready to be used Docker Images for this example to simply testing in different cloud providers). There is some important work around APIs, Deployments to different cloud providers, Application Service and Modelling Services all good places for getting started as a community contributor.



@igdianov worked on WS security PoC for graphql subscriptions.

@daisuke-yoshimoto interrupted investigating about Message Throw Event Behaviour and experimentally started to implementing Signal Throw Event Cloud Behavior.

@constantin-ciobotaru investigated usage of spring-cloud-kubernetes-discovery with spring-cloud Finchley.M5and spring-boot 2.0.0.M7 in activiti, added deployment descriptors for modeling service, updated postman collections, working for fixing swagger in modeling service

@mteodori adding the Meterianbadge to repos #1734

@lucianoprea worked on support for validate BPMN models #1720in process-model-services

@ffazzini deployed activiti to PKS and reported to Pivotal few problems with elasticsearch and kubectl command outputs, fixed the last swagger issues in activiti

@balsarori fixed 6.x UI startup issue,reviewed & merged 5.x PRs regarding historic persistence #1612

@ryandawsonuk Set up a rabbitmq docker image with stomp plugin enabled so that it is deployed with and used by the rest of the Activiti components and disabled websockets for deployments where the stomp plugin isn’t currently available (and trying to find out how to make it available). Documented how to run notifications for GraphQL in a separate container from query. Produced an RFC document for access control on the REST part of the query module.

@erdemedeiros worked on a PoC to support an additional media type that provides response contents in conformance with Alfresco Guidelines for REST APIs ( Good progress in the response content itself, but there are some challenges regarding pagination.

@salaboy worked on the trending topic blueprint (, moved it to a new repo and added more endpoints to each microservice to have more control over the scenario. I also attended the Makers Faire Lille, France where we printed the brand new Activiti & Activiti Cloud logo using a Portrait Painter Robot:


Check the February milestone to find the issues that we are currently working on this month and get in touch if you want to contribute:

We are looking forward to mentor people on the technologies that we are using to submit their first Pull Request ;)

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

On behalf of the team, I am pleased to announce that Alfresco Process Services 1.8 has been released and is available now. This release includes new features, improvements as well as important bug fixes. Here are a few notable highlights:



Process Workspace: New End-User Experience Based on ADF 

The Process Workspace is a new out-of-the-box user interface for end users to view, act and collaborate on tasks and processes. The existing UI is still available but the Process Workspace brings the following benefits:

    • It supports multiple screen sizes including mobile, tablet and desktop devices,
    • The user experience has been modernized and optimized to reduce  the number of clicks or taps to interact with tasks and processes,
    • And last but not least, it has been developed using the latest version of the Alfresco Application Development Framework (ADF). By doing so we are not only drinking our own champagne but the value for customers and partners also reside in the availability of the source code. Indeed,  they can use it as an example and extend it for their own ADF-based web application.

The Process Workspace UI is available at http://(hostname):(port)/activiti-app/workspace/.


Screenshot of the Process Workspace on a desktop screen.


Screenshots on a mobile screen.


Alfresco will continue to develop and extend the Process Workspace making use of the latest ADF developments. If you are not familiar with ADF, the standards-based javascript framework for quick web app development, you will find lots of useful resources on the dedicated community space. Please note that the Process Workspace is an optional experience. Current applications built on activiti-app are not affected.

New Elasticsearch REST Client

APS 1.8 now includes a new Elasticsearch REST client in addition to the 2 existing methods (embedded and client cluster). This allows the indexing of process event in external Elasticsearch environments including managed services such as AWS Elasticsearch. Please note that the previous configuration (the Java client) configuration is enabled by default and is still required if you want to use out-of-the-box reports from the Analytics App.


The REST client internally uses the Apache HTTP Async Client to send HTTP requests. This allows communication with an Elasticsearch cluster through HTTP. Here is an example of the required configuration to send data to an AWS ES domain.



event.processing.cronExpression=0/5 * * * * ?
event.processing.expired.cronExpression=0 0/10 * * * ?


After having restarted Process Services and launched new process instances, you can open Kibana and start visualizing process events you generated. For example, the Kibana pie chart below is showing the count per activity (e.g. start event, user task, script task, etc...) across all process instances that are running or that are completed.


Example of Kibana pie chart based on AWS Elasticsearch indexed data.


If you are not using Kibana but just want to quickly verify the data that was sent to the configured AWS ES domain. Here are some requests you can try directly in your web browser:



Completed tasks<tenant_id>/completed-tasks/_search?pretty

Process instances<tenant_id>/process-instances/_search?pretty 


Example of an HTTP request to retrieve the completed tasks.


NOTE: In the process engine database, the event data goes to ACT_EVT_LOG table and once processed (IS_PROCESSED_ = 1), the information is sent to Elasticsearch.

Complex Data Mapping 

This improvement enables non-technical domain experts to work closely with developers. They can model complex data scenarios so that customizations becoming configuration in repeated projects/processes rather requiring the repeated involvement of development. Specifically, this capability covers the export of data from a custom form stencil to any external system when using custom data models.


For example, you can design a custom form stencil with all the fields that describe an employee (e.g. id, contact info, job title, salary, etc...) and map them with the corresponding entity attribute of your data model. Here is an example of custom stencil runtime template for an employee object with 3 fields: id, name, and salary.

Here is the controller script.

Here is the custom data model for the employee.

Using the Store Entity task in your process, here is how you set the mapping. You only need to set the field value path to set the values you want to store from your object.


Code snippet for the storeEntity method of AlfrescoCustomDataModelService implementation showing how to extract the field value path.

Administration Console Enhancements

  • ‘Read-only’ Admin

A new setting in the Admin Console allows the creation of read-only admin users. This new capability targets authorized troubleshooter in your organization, people that can help others debug problems without accidentally altering information via the UI and potentially breaking operational processes. Please note that “read-only” users are still authorized to make changes through the APIs but not from the UI.  This new feature is thus a convenience feature to avoid accidental changes to the system by trusted users.

  • Download binary process data

As an administrator, you can now download binary process data and uploaded files from the Admin Console. This capability will help you when a process has gone wrong and you need to troubleshoot the problem.

For a complete list of improvements and instructions, please check out Alfresco documentation. Interested in trying out this new Process Services version? Register for a free enterprise trial here.

Almost 8 months of heavy work (and 6 Early Access Releases) we are happy to see that our building blocks are maturing to support more complex use cases. We are committed to improve each service iteratively and for that reason we are planning to have a live demo environments where we can push new versions our services in a continuous deployment fashion. [View official and updated Activiti & Activiti Cloud Roadmap here]

We are now working hard in our BluePrint example where you will be able to find a practical example about how to implement a real life scenario with Activiti Cloud.

We are keeping a close eye to issues reported to GitHub, to make sure that all of them are triaged and assigned to a milestone where someone from the team or our community contributors can take care of them in an ordered fashion. Check our current milestone for more details: We also created a new label for community contributors who want to get started with simple tasks called "community contributions":

Our focus remains: 

  • Create RFCs for new Cloud Native components and services
    • New App Definition And Lifecycle Management Service RFC coming
    • New BluePrint RFC coming
  • Provide a clear specification (APIs) about our Services (REST/Message Based/Configurations). Make sure that these APIs have well defined responsibilities, single focused and can evolve over time without causing consumers any headaches.
    • We iterate each component to make it simpler, faster and better
  • Make sure that we use standard tools, patterns and development techniques widely adopted by other Open Source Projects/Communities. Spring, Spring Boot, Spring Cloud, Docker, Kubernetes falls into this category, and we are making sure that we provide the right integration with these frameworks/tools. Activiti Cloud is designed from the ground up to work with such technologies.
  • Create Industry Specific BluePrints to demonstrate common scenarios and use cases that represent what different industries requirements.
  • Engage and mentor partners and community members that wants to participate.
  • Doing it in the Open Source way (Transparency & Meritocracy are a must).

Milestone #6- January 2018 - Ended -

  • Process Runtime Service APIs (review and proposal)
  • Notification Service initial implementation for release
    • Query Module now use GraphQL to provide faster and better options for data retrieval
  • Improved Activiti Cloud Connectors Starter
    • Connectors now use dynamic binding to improve traceability
  • Kubernetes ConfigMaps Research
  • Improved Deployment Descriptors for Kubernetes
    • Tests in AWS environments using our Helm Charts
    • Tests in PKS Pivotal Early Access Environment
    • Shared Helm Charts with the Alfresco Platform Services for core infrastructure

January was all about testing our infrastructure in real environments. The team also presented at DevCon (Alfresco Community Conference) where our Trending Topic Campaigns BluePrint initial version was demoed. We will be writing more about our BluePrint soon, and we look to hear from you what would you expect from it.

For now you can look at our slide decks and feel free to ask in gitter for more details

Activiti & Activiti Cloud Overview

[slideshare id=86282838&doc=activitiandactiviticlouddevcon-180117123046]

Activiti Cloud Deep Dive

[slideshare id=86287790&doc=activiticlouddeepdive-180117142105] #7- February 2018 - In Progress -

  • Process Runtime APIs (proposal and initial draft )
    • Process Engine Clean ups and refactoring
    • Cloud BPMN Throw/Catch Signals
  • Application Service (proposal and initial draft)
    • Definition
    • Lifecycle Management
  • Process Modelling Services next iteration
  • Research and initial integration
  • New Application Gateway research (support Eureka, Spring Cloud, WebSockets)
  • Kubernetes Service Registry and Service Brokers/Catalogs review

February will be all about APIs and a high level concept of an Application. The main purpose of these new services and APIs is to ensure that we have a coherent set of functionalities that can we can maintain consistent with future releases. The definition of what an application is going to define how our building blocks are configured to solve a set of business requirements. This definition will also define how this application will be maintained and upgraded in time. #8- March 2018

  • Security & SSO review (review Apache Shiro Wildcard Permissions)
  • Application Service (Add Case Management Constructs)
  • Deployment Service & Pipeline (Design and initial implementation)
  • JHipster Microservices Infrastructure Integration

Note: Activiti & Activiti Cloud Beta Release Prep Work

Milestone #9 - April 2018

  • BluePrint Trending Topics Campaigns User Interface and Dashboards
  • Polyglot MicroProcessRuntime PoC
  • JHipster Microservices Infrastructure Integration (based on Spring Boot 2) #10 - May 2018

  • Decision Service initial draft implementation
  • Forms integrations
  • Pipelines Support for deployments

Milestone #11 - May 2018

Note: Activiti & Activiti Cloud Final Release Prep Work

As always, if you want to participate on the development process of some of these components or examples get in touch. We are willing to collaborate with the open community and mentor people that want to learn about the project.

We look forward all community involvement, from comments, concerns, help with documentation, tests and component implementations. If you are looking into getting started with the Early Access Release we recommend to check our Getting Started Guide in Gitbook:[Getting Started · Activiti 7 & Activiti Cloud Developers Guide]

You can always find us in the Gitter channel: [Activiti/Activiti7 - Gitter]

Because we are a world wide community you can always find someone online to chat with, no matter your timezone

I’m happy to announce that Activiti & Activiti Cloud 7-201801-EA artifacts are out. We encourage our community members to try them out and provide feedback.

This release was focused on adding the third iteration for our Activiti Cloud Connectors, improving Tracing and Distributed Logging capabilities as well as expand on features to make sure that each of our service can scale in clustered environments. We keep iterating on our new services for process models and groups. Our GraphQL support in the Query module is now available for testing purposes, we look forward to your comments and feedback about these improvements and features.

We spend a fair amount of time deploying all our building blocks to an AWS environment to tune each block for best performance. This initiative is being executed in conjunction with the DBP platform team from Alfresco, and you can read more about our plans regarding this here DBP Platform Team and the Anaxes Shipyard Project.


As part of this release we aligned our artifacts with [Spring Boot 2.0.0.M7] and [Spring Cloud Finchley.M5]. It is important to note that Spring Boot 2.0.0.RC1is already out but Spring Cloud is still behind and not using it. As soon as they update we will update to use their latest released artifact.

The third iteration of Activiti Cloud Connectors was released as well, extending bidirectional channels and using dynamic bindings to use dedicated channels for each connector.  You can find more details about how to implement and interact with Activiti Cloud Connectors here.

Our Query module was augmented with GraphQL which currently provide a single endpoint for executing queries and a subscription mechanisms to provide push notifications to its clients. For more information about GraphQL take a look here. We are looking forward to add all these capabilities in our Blue Print example.

We are also putting a lot of effort in creating a BluePrint (Trending Topic Campaigns)example that demonstrate all our infrastructure in action, so we can iterate each block and their interactions. Our Blue Print Project can be found here:

We presented the initial draft of this BluePrint at Alfresco's DevCon and you can find the slides here:
- Activiti & Activiti Cloud Overview
- Activiti & Activiti Cloud Deep Dive

This BluePrint project can be deployed using Spring Boot, Docker Compose and Kubernetes deployment Descriptors and Helm Charts. We encourage our users to check this BluePrint project to understand more about new features and to help us to polish some rough edges. We are looking forward to have some nice Angular 4 UIs soon.

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

[We updated our Roadmap and included new Milestones]


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

Last week we closed several issues that we wanted to include in our January release.  @ryandawsonukdid an amazing job at releasing and documenting the procedure for our monthly releases which we will follow from now on, making sure that each member of the team can release when necessary. @erdemedeiros manage to finish some major improvements on connectors and @ffazzini introduced our microservices acceptance tests which will help us to improve the overall quality of all our modules. You can check out the release notes HERE



@igdianov was looking into security/authentication for websockets and gateway support for websockets.


@daisuke-yoshimoto continued to the Investigation for #1687that signals are exchanged cross multiple Runtime Bundles(each database).Together he are also considering about Intermediate Throwing Message Event for #1691.


@constantin-ciobotaru tested the spring-cloud-kubernetes-config functionality in activiti services inside kubernetes in the context of spring-cloud Finchley.M5and spring-boot 2.0.0.M7


@mteodori adding the snyk badge to repos #1615


@lucianoprea did some improvement investigations about sleuth and logging #1688and start looking into add validation endpoint for Process Model Service #1720


@ffazzini finished the poc on acceptance tests ( Also tried out activiti cloud deployment spike on pivotal PKS


@balsarori closed some community issues around throw/catch signals which was merged to 5.x branch


@ryandawsonuk Enabled turning off of graphQL and notifications via a property and carried out the monthly release.


@erdemedeiros finished work to get connectors using dedicated channels (, and updated related documentation (; Created a reproducer for a trace id issue at Spring Cloud Sleuth (


@salaboy worked on the Application Service first draft a RFC blog post is coming right after the release post.


This week we will be planning the February milestone, so if you want to help us to shape the future of the project get in touch.


Ping us in Gitter if you want to contribute:

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

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 &amp; 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:

In this short post, I’ll outline the steps to launch an all-in-one installation of Alfresco Process Services (APS) using our CentOS 7.2 Linux Amazon Machine Image (AMI) available from the AWS Marketplace.

Step 1: Visit the AWS Marketplace

From the AWS Marketplace page, search for the Alfresco products.

 AWS Marketplace

Select Alfresco Process Services (BPM), then click on the Continue to Subscribe button to access the software launch wizard.


Step 2: APS “1-Click Launch” on EC2

Using the “1-Click Launch”, you only need to select the region of your choice and can keep the default values for the other settings, (e.g., EC2 instance type, VPC settings, security groups and key pairs). Please ensure that this AMI is deployed to a public-facing subnet. The public subnet automatically assigns public ip addresses so the instances are accessible over the web. If you deploy the instance in a private subnet, you won't have web access to the instance.

EC2 launch wizard

Click the Launch with 1-click button. A confirmation page informs you that an instance of APS is being deployed on EC2.

Click on the ‘EC2 Console’ link in the green banner at the top of the page to navigate to the AWS EC2 Console, and select, from the instance list, the instance that you have just launched.

The EC2 instance will be in the ‘initializing’ state for no longer than 2 to 3 minutes, before APS will be accessible, denoted by the EC2 instance changing to the ‘running’ state.

Confirmation page 

Select the Description tab of your newly created instance and click on the Security groups link. Edit the Inbound rules and add a custom rule with the following values:

  • Type: custom TCP
  • Protocol: TCP
  • Port Range: 8080
  • Source: My IP

Security inbound rule

Step 3: Logging in to APS


Once the instance state is ‘running’ and all status checks passed, open a browser page using the URL: http://{public_dns_here}:8080/activiti-app.

Login page 

On the login page, use the credentials:


If you need a valid product license, it takes less than 2 minutes to get a 30-day trial license by filling out the form at

Step 4: Logging in to APS Admin console (optional)

Open a browser page using the URL: http://{public_dns_here}:8080/activiti-admin. On the login page, use the default credentials: admin/admin.


Once logged in to the Admin console,  it is always recommended to update the existing password to something much more secure such as a combination of four words. Check out this post for details about securing passwords.


Open the Configuration menu to connect the Admin Console to your APS running application. Edit the REST endpoint settings and apply the corresponding values as shown here below.

REST endpoint configuration 

Save and click on Check REST endpoint. You get a confirmation message with the endpoint status and Engine version.


Bravo! You have successfully launched APS using the AMI published by Alfresco. You now have a running APS environment that you can use to explore the Hello World getting started tutorial and try out some of our more advanced community examples.

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.

(18/12/17 - 24/12/17) We’ve been working hard to eat our own dogfood by fleshing out our Trending Topic Campaigns example to make it as realistic as possible and testing it at high volumes. This is helping us to refine the Activiti Cloud tooling and provide better guidance on how to use it.



@daisuke-yoshimoto worked through issues and forum questions, helping make progress on issues experienced in the community

@constantin-ciobotaru worked on building an executable for the Activiti Cloud Models module to run in a docker container

@mteodori addressed a vulnerability by removing an unnecessary xerces dep from v5

@lucianoprea worked on building an executable for the Activiti Cloud Organisation module to run in a docker container and flushed out some issues in our gitbook instructions

@ffazzini fix zipkin Boot M7 breaking changes, memory/performance optimisations for applications running on minikube

@balsarori offered advice to help resolve a key issue with the connector implementation

@ryandawsonuk did some refactoring of the trending  Trending Topic Campaigns example and integrated ELK into the example

@erdemedeiros did some code reviews and investigated a random failure around the connector examples. Will be on holidays next week.

@salaboy did some planning for work on the trending topics example and further work into next year as well preparing presentations


Ping us in Gitter if you want to contribute:

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

(11/12/17 - 17/12/17) We are getting close to the end of the year and we are focusing on improving our tests and building blocks. We want to start 2018 with a continuous deployment approach for our services and tools that we build. For that reason, we are spending some time in setting up our Trending Topic Campaigns example (which uses Docker & Kubernetes) in an environment that we can run, test and validate our releases.



@daisuke-yoshimoto added ability to activiti-cloud-runtime-bundle-service to start a process instance by process definition key and business key. Also, he is reviewing the following pull requests.

Fix signal events throw/catch race conditions in transaction scope

Update the persisted historic task instances that are open

@constantin-ciobotaru worked for connectivity between organization service and model services (like process model), added modeling backend starter and improved versioning on process models service

@lucianoprea worked on the  Activiti Cloud Service Organization having the first iteration merged and almost done the Spring Rest Docs integrated for the Audit JPA

@ffazzini spring profiles for logging, Boot M7 breaking changes fixes, investigation around terraform/rancher deployment for having an environment up and running

@ryandawsonuk has been reviewing contributions and checking the latest builds and updating after a recent spring boot milestone upgrade

@erdemedeiros did some bug fixes and worked in the trending topic campaigns example.

@salaboy working on updating our gitbook ( ) and looking into our modelling backend services. I helped also with reviewing and refactoring some of the bits inside of the Trending Topic Campaign Cloud Examples.



This week, we will start preparing for our December release, which is full of fixes and most importantly our demo scenario that demonstrate how to build, deploy and scale domain specific Activiti Cloud Applications. I (@salaboy) will be off for 3 weeks so I hope to see you all at DevCon ‘18.


Ping us in Gitter if you want to contribute:


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