PaaS Partner Community

  • October 11, 2015

Video on Using Force Commit for Non-Idempotent Activities in BPM 12c by Jaideep

Juergen Kress
PaaS Partner Adoption

clip_image002In 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. Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.