This is about how to create case management solutions with Camunda BPM. You will get a crash course in CMMN and understand the typical architecture of the accoding applicatins. Combining BPMN and CMMN will also be covered.
2. 10+ years experience with workflow and Java EE
Co-Founder of Camunda
Evangelist
Head of Consulting
@berndruecker
bernd.ruecker@camunda.com
Bernd Rücker
3. Published by OMG in May 2014 as the BPMN-equivalent for „Cases“
„Activities that are not so predefined and repeatable, but instead
depend on evolving circumstances and ad hoc decisions by knowledge
workers regarding a particular situation”
Typical Use Cases:
−application and claim processing in insurance
−patient care and medical diagnosis in healthcare
−exception handling, e.g. problem resolution in call centers, invoice
discrepancy handling, data validation errors, …
See http://www.omg.org/spec/CMMN/1.0/
Camunda shipped CMMN 1.0 implementation with 7.2
CMMN
7. Example: „Underwriting“
There are workarounds – but
this is hard to model in BPMN.
You need more flexibility for
the „Knowledge Worker“
It is hard to give a stable
ordering of the tasks!
Flexibility needed.
100 % standardized –
no flexibility needed
9. CMMN explained
Human Task –
automatically
activated
Process Task –
manually
activated
Milestone
Sentry – controls if
the Milestone is
reached
Sentry – controls if
the User Task is
enabled
Connector – to
visualize
dependencies
(no sequence flow!)
11. BPMN Standard does not (yet) support CallActivity for CMMN
Camunda will introduce this with 7.3
Workaround recommendation for now:
Alternatives:
You can replace the Service Task by an Execution Listener if you
prefer
You can hack the CallActivityBehavior
BPMN calls CMMN
12. Defined by CMMN Standard – no workarounds necessary
CMMN calls BPMN
14. Example UI for Case Instance
Task Form – to work
on Human Task and
see context from case
Case Context (could
show or link more
information)
Case Activities –
provided by engine,
correspond to lifecycle
19. CMMN might be more complex (and powerful)
Sentry might take
data (variables)
into account.
A stage is one
„phase“ in the
case.
Exit Criterias can
mark results of a
case.
21. Current Toolchain
CMMN
Web Modeler
Developers DIE
(e.g. Eclipse)
Engine /
Application Server
Own application
with User Interface
Camunda Cockpit
with ACM Plugin
CMMN
File
+ PNG
Normal deployment
(e.g. WAR)
API
(Java or
REST)
API
(Java or
REST)
22. Cockpit Plugin
available via Plugin Store:
camunda.org/plugins
Special thanks
to our partner
Holisticon & Simon
Zambrovski
23. Gain more real-life experience and collect feedback
Work on CMMN coverage (Required, discretionary, events, …)
Add Cases to cockpit
Add CMMN-Modeler (on bpmn.io basis)
Next steps and further ideas
Disclaimer: No fixed roadmap decided yet.
27. But it is important to distinguish
1.
You have „Knowledge
Workers“
2.
You are missing
discipline!
28. Often a question of maturity
End-to-End Process
End-to-End Process
some
reamining
manual work
GOAL
(in 10
years)
NOW
Automated
Snippet
Automated
Snippet
29. Scaling your business with BPM!
Zalando
Founded: 2008
Employees: 7000
Revenue: 1,8 billion EUR