Data directive code block execution rules

What’s the difference between the Execution Rule options on a data directive code block? (“Synchronously execute custom code… with rule”, clicking “with rule” brings up a dialog.) The enabled choices are “Once passing all matching rows” and “Once passing all existing rows”. Under what circumstances would there ever be more than one updated row? What do “matching rows” match, and what does “all existing” mean if not all rows in the table?

I wonder if you can give us more detail?
e.g. which version of E10 you are running, maybe screen shots of BPM forms/components?

In a In-tran DD, the Execute Custom Code widget has two choices:


in a Standard DD, there is also a "with rule" setting, which provides the following pop-up


That pop-up is the same, regardless of sync or async selection.


I too would like to know what these do, and when the defaults need to be changed.

1 Like

Thanks, I knew I’d seen it before but could not remember where.

There is a section in the embedded help that (I think) explains what is going on there.
Ref screen shot…

And now that I’m looking, this I wonder if this option might help resolve a change request to the way some old BPM’s are sending emails. TBD…

1 Like

Multiple Dirty Rows (BPM Workflow Designer > General Principles > Multiple Dirty Rows)
SOME methods can send multiple dirty rows together as a set to the server for update

Just an FYI…
I found a few, threads on this site that were helpful (to me anyway)
when searching for “Multiple Dirty Rows”
e.g. Support for multiple dirty rows