Calling Stored Procedure from BO Rules

[customaware]

Not sure if this should work or not but I have a BO with many BO Rules and many of those rules are updating with the SUM and COUNT functions.

These slow the updating of the BO down a lot so I was hoping to pass this off to a Stored Procedure...

But my concern is that we normally need to add a COMMIT TRANSACTION after the Stored Procedure has run.
But of course, in the BO Rules, Aware has not yet written everything back to the DB. So, the SP will be reading values from
the DB but some of these "may" have been updated in an earlier BO Rule. Likewise, subsequent BO Rules will not know the
values in the DB that the SP has updated.

This leads me to think that it is both a bad idea and most likely will not work.

Am I right in this thinking or is there a best practice way of doing it?

[BLOMASKY]

Mark, generally I need a commit transaction BEFORE (not after) I call a stored procedure. That way any data that is either entered (or computed by a rule) in Aware are saved to the database. Since I do that before calling the SP, any aware processing afterwards will (re)read the appropriate records from the db. Most of the time, I will have a process calling a stored procedure. Even if I have a rule call it. I name my processes that call a stored procedure to start with SP_procedureName. That way I can always find them.


Bruce

[customaware]

Good suggestion Bruce.

I will try that out.

[ACDC]

I am busy with the same thing, would it not be better to use a Trigger for SUM and COUNT purposes ? ( based on UPDATE)

[customaware]

Never used Triggers.

Bruce, do you put the COMMIT TRANSACTION in the BO Rule and then call the SP process or do you put the COMMIT TRANSACTION as the first action on the SP Process…. Or doesn’t it matter?