Using Force Commit for Non-Idempotent Activities in BPM 12c

In BPM 11g it was not possible to explicitly ask the engine to dehydrate the bpm process instance state. The only way to do this was to model a timer catch event set to one second or longer. Oracle BPM 12c has introduced a new property for activities called ‘Force Commit after execution’ to enable us to do this. This video is an excerpt from one of our Oracle BPM Training courses which explains why this property is important especially when you have Non-Idempotent activities in your process. You can see out entire Oracle BPM Training Course catalog at http://training.fusionapplied.com/oracle-bpm-training-course-catalog/ If you are interested in training be sure to sign up for Free Lessons and Training Discounts at http://training.fusionapplied.com/