On Wed, 25 Jan 2012 10:58:17 -0800, David Swearingen <[email protected]> wrote:
> We have a working pipeline with a condition element and an action > element, as would be expected. We now need to in essence add a second > condition, where we would need both conditions to be evaluated, and if > either returned true, then the same action gets executed. > > We do NOT wish to change the logic of the first condition (the .xqy > file) for reasons I won't get into here. > > Is there a way to do this? We tried adding a second state-transition > element, but that appears not to work, and this was just speculation > since we can't find any documentation to support doing this. Adding another state transition for the same state could work: they will be checked in document order. It is easier just to add additional execute blocks to your existing transition. You can have as many execute blocks with conditions/action pairs in a transition as you like. They will be tested in order, and the first successful condition causing the associated action to be invoked. If none of the conditions returns true, the default action will be invoked. See, for example, the Status Change Handling pipeline or the XInclude Processing pipeline. //Mary [email protected] Principal Engineer MarkLogic Corporation _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
