Last week (16/10/17 - 22/10/17) we started several initiatives to define a new set of services to support our new set of tools. We started by creating a specification document (public) to define how the Process Model Service is going to work. We also move forward some changes on the default behaviors for the process engine, such as use UUID for ID generators and the default Service Task behavior when running inside a Runtime Bundle. We manage to merge a PR vital to push Activiti Cloud Connectors forward and a new Activti Cloud Connector Starter was created.
@willkzhou was experimenting with ElasticSearch and getting used to the new repository structure.
@igdianov started looking at graphQL subscriptions and we started discussing about how to create a notification mechanism for the entire platform.
@constantin-ciobotaru started looking at Spring Cloud Contracts and an initial version for the Process Model Service.
@lucianoprea started looking at Spring Rest Docs for our runtime bundles.
@balsarori worked on modifying the default Activiti Cloud starter configurations (removed unnecessary properties and enabled UUID generation by default). Additionally, started working on first version of Activiti Form Runtime Service.
@ryandawsonuk documented how to secure Activiti endpoints using keycloak, started planning implementation of security by process definition and worked on changes to the release process to support using jgitflow
@erdemedeiros worked on message queue implementation for service tasks. After a further investigation the correlation id seems no longer necessary and was replaced by the execution id. The related pull request is the end of the review process and should get merged soon.
@salaboy I’ve spent most of the week validating that the repository refactoring didn’t affect any module. I’ve also added new sections to our gitbook about each service and how we are going to adopt GitFlow as our main way of interactions with community and team members.