processi

about processes and engines

over-if

Mars had an idea and I implemented it, as it is simple and makes process designers’ life easier.

(note : a process designer is a function, a role, not a profession, this term was the first to come to my mind, but other ‘appellations’ are possible, the bpm infosphere is full of them)

Mars needs an easy and readable way of terminating a concurrence on a condition.

    <concurrence
        over-if="${f:disagree} != ''"
    >
        <participant ref="nicolas" />
        <participant ref="olrik" />
        <participant ref="pedro" />
    </concurrence>

As soon as one of the participant will fill the ‘disagree’ field of its workitem and reply (proceed), the concurrence will be over and other branches will be cancelled.

This new ‘over-if’ attribute is documented with its <concurrence> expression (yes, it works with <concurrent-iterator> too).

‘over-if’ can be used with the classical ‘count’ attribute, meaning that you can terminate a concurrence as soon as a certain number of branches replied or as soon as the ‘over-if’ condition verifies.

Talking about making the life of a process designer easier, I read that post from Bruce Silver, and I felt a bit shocked when reading ‘lesson 3’, OpenWFE is able to do that since at least three years.

Written by John Mettraux

July 20, 2006 at 7:13 am

Posted in bpm, openwfe, workflow

%d bloggers like this: