Hi Thong.
Business Data is your responsibility to save. Normally projects leverage the Java ecosystem to do that, e.g. JPA (Java Persistence API) in a Java EE environment. You need some Java knowledge to do so (see why: http://camundabpm.blogspot.de/2013/04/the-camunda-hypothesis.html). An example can be found here (in German – but that should not matter in that case): https://github.com/camunda/camunda-bpm-examples/tree/master/bestellprozess-java-ee6.
For what you call flow objects we use a Map within the process engine, hence you can always store, read and change variable values via the API of the process engine during runtime. You cannot model the flow objects in the BPMN process model! So again, this information will go to the Java code. We do this to gain maximum flexibility in data handling and because this turned out to work extremely well in BPM+Java projects. Understandable what I mean?
Cheers
Bernd
Evangelist & Consultant
--
You received this message because you are subscribed to the Google Groups "camunda BPM users & process application developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to camunda-bpm-us...@googlegroups.com.
To post to this group, send email to camunda-...@googlegroups.com.