Beta4 included an upgrade to Spring Boot 2.1 and Spring Cloud Greenwich.M3. For any applications built on Spring Boot 2.0.x, it is recommended to upgrade Spring Boot along with Activiti 7 version.
This is a great time to get involved to help us with the Beta testing process, integrating with your favourite Open Source projects and learning about the technology stack that we are using to build these amazing tools. If you are ready for a big challenge get in touch via Gitter.
For deployment to Kubernetes, Helm charts are provided in https://github.com/Activiti/activiti-cloud-charts and these can be consumed using the https://activiti.github.io/activiti-cloud-charts/ charts repository, as suggested in https://github.com/Activiti/activiti-cloud-charts/blob/master/activiti-cloud-full-example/README.md
With Beta4 the charts version moved to 0.5.x
To enable the modeling UI, add:
To the myvalues.yaml file used for deployment of the full example. Access the modeling UI on the
/activiti-cloud-modelingpath of the gateway host.
The version of maven aritfact
activiti-cloud-dependenciesshould be upgraded to
7.0.0.Beta4Also the CreateTaskPlayload interface changed to enable Task creation to include Candidate Users and Candidate Groups. This change affected the get/setGroup() method which now looks like this: https://github.com/Activiti/activiti-api/blob/develop/activiti-api-task-model/src/main/java/org/activiti/api/task/model/payloads/CreateTaskPayload.java#L107
So get/setGroup needs to be update to get/setCandidateGroup().
Currently Spring HATEOAS output for Activiti Cloud services is incorrectly showing cluster-internal URLs for self links. This is a bug in Spring HATEOAS for which the fix has not yet been released (at the time of writing). We expect this issue to go away when we upgrade to Spring Cloud Greenwich.RELEASE.