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.


Jaideep

Jaideep has more than 20 years of professional software development experience. He has delivered solutions for several domains including financial services, e-Government, criminal justice, and wireless application services. He is a Certified Scrum Master and has mentored several teams to use agile software development techniques. He has delivered several SOA/BPM solutions based on the BEA/Oracle SOA Suite over the last 6 years . His current focus is on helping customers build solutions using Oracle BPM, Webcenter, ADF and SOA Suite 11g and 12c. Jaideep also trains teams on using Oracle BPM and has developed several self paced online video training courses for Oracle BPM 11g and 12c.
Jaideep

Leave a Reply

avatar
  Subscribe  
Notify of