No transactions for any SQL executed

All SQL you yourself execute in Metastorm BPM 9 is executed outside of the transaction. If the event you are in rolls back for any reason, including use of UserError, the executed SQL is not rolled back.

 

This seems like a very large oversight. This was introduced sometime in version 5, IIRC.

 

Is this acknowledged, or is it a bug, and are there any plans to fix / change this behaviour?

Tagged:

Comments

  • Agreed that this is a very scary condition.  Sometimes actions are "do a" "do b" "do c" and if c errors all should be rolled back.  If they are not treated as a single transaction (as they would have in v7) you could end up with bad data -- and no real method to detect or fix (if possible).

  • Hello
    Is there any news from OpenText/Metastorm employees?

  • This is a longstanding issue with WF in .NET 3.5.  Essentially, the issue is that the hosted WF environment could not participate inside the overlying DTC transactions.  I know the team has done a ton of work to upgrade to .NET 4.0 in order to resolve this issue, so hopefully we'll see the fruits of this work soon.  Maybe 9.1.3?