11. Internal Presentation11
What to expect?
●
Core engine
●
Case mgmt improvements to core engine
●
Kie-server case extension
●
Authoring
●
Additional Designer properties
●
Case Modeler
●
Runtime views
●
Case list
●
Case details
●
Custom applications
18. Internal Presentation18
Case Modeler
●
Focus on specific subset of cases
●
Target non-technical users
●
Reuse some of Designer.NEXT properties for activities
●
Alternative visualization of underlying BPMN 2.0 model
●
Switch to full designer for additional details
23. Internal Presentation23
Custom applications
Rather than trying to create one web application
that all customers can use out-of-the-box,
offer creating custom applications, reusing as
much as possible of what we offer
Hi, my name is Kris Verlaenen and I'm the jBPM project lead. The jBPM project is a completely open-source BPM project and there's also a supported offering based on this by Red Hat called JBoss BPM Suite.
Hi, my name is Kris Verlaenen and I'm the jBPM project lead. The jBPM project is a completely open-source BPM project and there's also a supported offering based on this by Red Hat called JBoss BPM Suite.
Hi, my name is Kris Verlaenen and I'm the jBPM project lead. The jBPM project is a completely open-source BPM project and there's also a supported offering based on this by Red Hat called JBoss BPM Suite.
What I would like to present today is how we are including support for more adaptive and dynamic cases. We see this as an extension to processes, supporting more flexibility using more advanced features.
We believe that there is a wide spectrum of processes, from well-structured to completely dynamic, where nothing is defined upfront, and that there is no line between where a process ends and where a case starts.
The approach we have taken is to add support for these more advanced features, that aren't unique to cases, on top of what we already have, a flexible process engine based on BPMN 2.0.
Those screen components get their information from our intelligent process execution server, that offers easy-to-consume REST endpoints to provide the data that is required and to interact with the cases.
In the demo I will present a simple healthcare example where a patient is followed across multiple stages of diagnosis and treatment, and it's the doctor who will be making all the decisions.
For example, our demo application consists of a UI that is custom built for our use case. As you can see it's using healthcare-specific concepts and everything can be customized to the detail.
But this UI is based on more generic building blocks for showing for example case details, milestones that have been achieved, case roles that are participating, tasks, etc.
Our workbench allows you to combine existing UI building blocks, like small screen components or reporting charts into these custom views and applications using drag and drop.
Administrators can extend the workbench itself with custom screens and entire perspectives, and expose their custom built applications to end users, either within the workbench or as separate applications.
By combining and customizing out-of-the-box UI building blocks, you are able to rapidly prototype and show immediate value during development of case applications.
Hi, my name is Kris Verlaenen and I'm the jBPM project lead. The jBPM project is a completely open-source BPM project and there's also a supported offering based on this by Red Hat called JBoss BPM Suite.
Hi, my name is Kris Verlaenen and I'm the jBPM project lead. The jBPM project is a completely open-source BPM project and there's also a supported offering based on this by Red Hat called JBoss BPM Suite.
Hi, my name is Kris Verlaenen and I'm the jBPM project lead. The jBPM project is a completely open-source BPM project and there's also a supported offering based on this by Red Hat called JBoss BPM Suite.
The approach we have taken is to add support for these more advanced features, that aren't unique to cases, on top of what we already have, a flexible process engine based on BPMN 2.0.