|
Home > Archive > BizTalk Server Orchestration > September 2005 > ODBA problem/limitation ?!!!
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
ODBA problem/limitation ?!!!
|
|
| Sandac 2005-09-27, 8:49 pm |
| Hi,
I start using Orchestration Designer for Business Analysts (ODBA) to create
orchestration and run in to ODBA problem/limitation.
According to ODBA documentation - help file:
"The Join shape should be the place where different branches of Decide/Fork
shapes come back together. BUT if you have a Join shape that accepts flows
from different Decide/Fork shapes, the checker catches this as an error and
flags it."
But It's one of the most common logic workflow.
How can use one Join shape to accept flows from different Decide shapes?
Any ideas?
Thanks.
| |
| Matt Cable 2005-09-28, 2:49 am |
| I believe the reason why is that it would not be possible even in the final
Orchestration. You would have to duplicate the logic or call out to another
Orchestration.
In BizTalk 2004/2006 Orchestration there is no seperate Join shape. There
basically is just join functionality by default at the bottom of each Decide
and other similar branching structures. As mentioned above, if would like
to reuse functionality across the branches you mentioned, you would have to
have those branches call out to another Orchestration that has common logic.
- Matt Cable
"Sandac" <Sandac@discussions.microsoft.com> wrote in message
news:5465E0EF-4D02-4197-97B7-A70567032F43@microsoft.com...
> Hi,
> I start using Orchestration Designer for Business Analysts (ODBA) to
> create
> orchestration and run in to ODBA problem/limitation.
> According to ODBA documentation - help file:
> "The Join shape should be the place where different branches of
> Decide/Fork
> shapes come back together. BUT if you have a Join shape that accepts flows
> from different Decide/Fork shapes, the checker catches this as an error
> and
> flags it."
>
> But It's one of the most common logic workflow.
> How can use one Join shape to accept flows from different Decide shapes?
> Any ideas?
> Thanks.
>
| |
| Sandac 2005-09-28, 2:49 am |
| Matt,
your wrote:
>"You would have to duplicate the logic..."
What do you mean by that?
and
"...or call out to another Orchestration."
Are you trying to say I have to have multiples Orchestration?
In my case I have very large orchestartion with a lot of Decide and Join.
If I need to introduce multiples Orchestration it would be to many of them
and very hard to manage them.
Thank you.
"Matt Cable" wrote:
> I believe the reason why is that it would not be possible even in the final
> Orchestration. You would have to duplicate the logic or call out to another
> Orchestration.
>
> In BizTalk 2004/2006 Orchestration there is no seperate Join shape. There
> basically is just join functionality by default at the bottom of each Decide
> and other similar branching structures. As mentioned above, if would like
> to reuse functionality across the branches you mentioned, you would have to
> have those branches call out to another Orchestration that has common logic.
>
> - Matt Cable
>
>
> "Sandac" <Sandac@discussions.microsoft.com> wrote in message
> news:5465E0EF-4D02-4197-97B7-A70567032F43@microsoft.com...
>
>
>
|
|
|
|
|