Video on 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.

If you like our videos and blogs, be sure to click on the buttons below to follow us on LinkedIn and Twitter so that you can get notified when we post new content.