Last week we worked to make further refinements in our core services. Events emitted by our services now include the Activiti Cloud Application Name, Service Type and version. Our new Runtime APIs are now covering Event Listeners and Connectors and we are getting close to start moving these initiatives from the incubator to their own repositories.
@MiguelRuizDevstarted tweaking with Angular in order to build a basic UI to try TaskManagerService out
@igdianovfinishing acceptance tests for GraphQL and subscriptions mechanism
@daisuke-yoshimotois working on making acceptance-tests for Signal Throw Event Cloud Behavior.
@constantin-ciobotarucreating new controllers for Modelling Service to support different backends for storage
@pancudaniel7start looking into Activiti7 by checking out the activiti-cloud-examples
@balsarorireviewing PRs and discussions around Service Task Binding behavior in the engine
@ryandawsonukcreated PRs to add application metadata (service name, version, type, parent application) to the events emitted by the runtime bundle and have these consumed by the other components. Included in the PRs changes to the security policies for these services so that service name can be specified in long or short format
@erdemedeirosworked on the new Process Runtime Java APIs. Polished events listeners; added the first iteration for Java connectors (work in progress).
@salaboyworked in splitting the Activiti Cloud Blueprint into separate repositories to leverage cloud deployments and automated pipelines for continuous delivery.
Also we will start merging code from the incubator to our infrastructure components to make sure that our Demos and Blueprints use the new services and features. We will also be having more news about our Modelling project soon, so keep an eye on this blog for more news soon.