transaction control

ddumas

Does Aware IM support grouping of processes, which may span multiple forms / processes, business rules, etc., into a single transaction, such that all succeed or fail as a unit?

Ex of logical process.

start transaction
do step 1
do step 2
do step 3
end transaction

If step 3 fails because of a business rule, or otherwise, , are step 1 and step 2 rolled back? If so, how is this controlled?

BobK

I had asked AwareIM support a similar question some time ago. I can not find their response, so the following is from memory and I make to guarantee on its accuracy 🙂

Under most conditions, changes to the database are committed after all processes in a chain compelete. So in your example, the database changes would be committed only after endtransaction. If anything failed before that, all processing would stop and any changes would be rolled back.

Some exceptions to the above.
1) If any process does a FIND and uses IN BATCHES OF, a commit is performed after each batch.
For example, if your "do step 2" executes the following:
FIND ALL bo IN BATCHES OF 1
UPDATE bo
If there are 10 instances of bo, there will be 10 commits performed, once after updateing each instance of bo. Any changes from "start transaction" and "do step 1" would also be committed.

2) If any process executes a REPORT ERROR, all processes in the chain stop and any changes up to that point are rolled back UNLESS the process has Failure rules. If the process has Failure rules and REPORT ERROR is executed: the Failure rules execute, processing continues and nothing is rolled back UNLESS the Failure rules also execute a REPORT ERROR.

ddumas

BobK wrote
I had asked AwareIM support a similar question some time ago. I can not find their response, so the following is from memory and I make to guarantee on its accuracy 🙂

Under most conditions, changes to the database are committed after all processes in a chain compelete. So in your example, the database changes would be committed only after endtransaction. If anything failed before that, all processing would stop and any changes would be rolled back.

Some exceptions to the above.
1) If any process does a FIND and uses IN BATCHES OF, a commit is performed after each batch.
For example, if your "do step 2" executes the following:
FIND ALL bo IN BATCHES OF 1
UPDATE bo
If there are 10 instances of bo, there will be 10 commits performed, once after updateing each instance of bo. Any changes from "start transaction" and "do step 1" would also be committed.

2) If any process executes a REPORT ERROR, all processes in the chain stop and any changes up to that point are rolled back UNLESS the process has Failure rules. If the process has Failure rules and REPORT ERROR is executed: the Failure rules execute, processing continues and nothing is rolled back UNLESS the Failure rules also execute a REPORT ERROR.

That makes sense. I would guess that all object changes occurring as a result of business rules "in the chain" become part of the transaction in a simple form based submit, and when additional defined processes are involved as part of that, those are included (paraphrasing from your response).

So, I am going to add another post that asks about concurency. handling, so as not to combine into this post.

Thanks.

ACDC

You can group processes by chaining them in one process. Create a process and then refer to each "process name" in the rule

aware_support

BobK reply is fairly accurate. There is a LARGE section in the User Guide that explains database transactions in Aware IM in detail. Please make sure that you read it!