| Author |
Call Orchestration from a Business Rule?
|
|
| Stuart A Hill 2005-03-11, 7:47 am |
| Hi all - is it possible to call rule engine to dynamically determine which
orchestration to call in the next step?
Thanks
Stuart Hill
| |
| Scott Woodgate \(MS\) 2005-03-12, 5:49 pm |
| You could do this behaviour with an orchestration that called the rules
engine and then used the result to figure out which nested orchestration
(using call/start) it wanted to call next. Beware of the granularity so you
aren't doing lots of trips to the messagebox...
The other way you describe isn't so easy.
"Stuart A Hill" <xyz@abc.com.bin> wrote in message
news:eT2o1NjJFHA.484@TK2MSFTNGP15.phx.gbl...
> Hi all - is it possible to call rule engine to dynamically determine which
> orchestration to call in the next step?
>
> Thanks
>
> Stuart Hill
>
>
| |
| Scott Colestock 2005-03-12, 5:49 pm |
| You could also do this by having your rules establish content in an outbound
doc that was used for content-based routing.
(i.e. you could set a promoted property, and the orchestrations that are
candidates for firing up can be filtering on this property. When you return
from the rules engine to your 'coordinating orchestration', send the
resulting doc via a direct-bound port.)
Scott Colestock
www.traceofthought.net
"Scott Woodgate (MS)" <replyto@newsgroup> wrote in message
news:eAIMEQzJFHA.1308@TK2MSFTNGP15.phx.gbl...
> You could do this behaviour with an orchestration that called the rules
> engine and then used the result to figure out which nested orchestration
> (using call/start) it wanted to call next. Beware of the granularity so
> you
> aren't doing lots of trips to the messagebox...
>
> The other way you describe isn't so easy.
>
> "Stuart A Hill" <xyz@abc.com.bin> wrote in message
> news:eT2o1NjJFHA.484@TK2MSFTNGP15.phx.gbl...
>
>
|
|
|
|