salaboy

Activiti & Activiti Cloud 7-EA201710 are out!

Blog Post created by salaboy Employee on Nov 3, 2017

I'm happy to announce that Activiti & Activiti Cloud 7-EA201710 are out and we encourage people in the community to try and report issues if you find them. This release was focused on improving our base building blocks to get the infrastructure working in Kubernetes and Docker based deployments.

 

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

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

Our building blocks highlights:

  • Runtime Bundles:
    • By default IDs are set to UUIDs.
    • Default behaviour for Service Tasks inside runtime bundles now emit IntegrationEventRequests and consume IntegrationEventResutls, which enables Activiti Cloud Connectors to react and perform system to system integrations.
  • Query Service
    • GraphQL endpoint added, now you can use the power of GraphQL to extract data from our Query JPA Service. This was provided by @igdianov
  • Audit Service
    • MongoDB implementation of our Audit Service was provided by @daisuke-yoshimoto
  • Cloud Connectors (Starter): and initial implementation for the Cloud Connectors was released as part of this release. You can use this starter to create a simple template of our Activiti Cloud Connectors.

We also included our first version of our JHipster Generator.
As part of this release the new GroupIds and ArtifactIds has been introduced based on our Repository refactoring. From now own, if a project depends on Spring Cloud it will be under the GroupId org.activiti.cloud.

We are quite happy with the current structure and it seems that it is going to stay stable for now. Even if we change the structure of the repositories we will maintain the groupIds and you should always point to activiti-dependencies and activiti-cloud-dependencies. In other words if you want to work with Activiti Process Runtime artifacts we do recommend using:

[code language='xml'] org.activiti activiti-dependencies ${version.activiti} pom import [/code]


And if you are looking to use Activiti Cloud Artifacts use:

 

[code language='xml']


 
   
      org.activiti.cloud
      activiti-cloud-dependencies
      ${version.activiti.cloud}
      pom
      import
   
 

[/code]

We still have some open RFCs that you are more than welcome to comment, we will be working on these topics for our 7-EA201711 release: 

Outcomes