<font size=2 face="sans-serif">Agreed with Jocelyn, I've successfully
implemented such an approach for an ISU workflow on my client project,
and it works very well. In my case, the SAP standard ISU events I
was interested in were BOR-based (I think they all are in ISU) , so I opted
to create a custom receiver to generate an equivalent OO event.</font>
<br>
<br><font size=2 face="sans-serif">Best Regards,<br>
James Johnson<br>
<br>
E-mail:JJohnson@uk.ibm.com<br>
Mobile: 07908715224</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Dart, Jocelyn"
<jocelyn.dart@sap.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"SAP Workflow
Users' Group" <sap-wug@mit.edu></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">09/05/2015 13:32</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: Dynamic
even in a wait step</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">sap-wug-bounces@mit.edu</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=3>Hi Mike</font>
<br><font size=3>Many moons ago we wrote an event receiver function module
that converted a BOR event into a OO event which saves creating event only
workflows</font>
<br><font size=3>Just a thought</font>
<br><font size=3>Rgds</font>
<br><font size=3>Jocelyn</font>
<br><font size=3><br>
Sent from my iPad</font>
<br><font size=3><br>
On 9 May 2015, at 6:49 am, Rick Bakker <</font><a href=mailto:rbakker@gmail.com><font size=3 color=blue><u>rbakker@gmail.com</u></font></a><font size=3>>
wrote:<br>
</font>
<br><font size=3>Hi Mike, </font>
<br>
<br><font size=3>How about have each of the wait events listed as a start
event of a workflow whose only step is to create a generic event to be
picked up by your main workflow?</font>
<br>
<br><font size=3>regards</font>
<br><font size=3>Rick</font>
<br>
<br><font size=3>On Fri, May 8, 2015 at 10:20 AM, Mike Pokraka <</font><a href=mailto:wug@workflowconnections.com target=_blank><font size=3 color=blue><u>wug@workflowconnections.com</u></font></a><font size=3>>
wrote:</font>
<br><font size=3>Hi Florin,<br>
<br>
Nice idea, I like it. It's sortof between my option 1 and 2 but cleaner.<br>
<br>
Another approach I'm considering is a bit more radical. It's a hybrid BOR<br>
and OO workflow precisely because of a multitude of events from Status<br>
Management, which still doesn't do OO-WF. I kept BOR in the WF because
I<br>
had it in my head that I could do dynamic waits for events straight from<br>
BSVW config.<br>
<br>
If the eventing in WF is too complex, I'm thinking an event forwarder into<br>
a pure OO workflow right from the beginning is probably better. With a
bit<br>
of subclassing*, I can reduce it to 3 or 4 event waits and a little<br>
consolidation logic in the event forwarder code.<br>
<br>
Still pondering, will post back what I finally decide on. Still open to<br>
other suggestions.<br>
<br>
Thanks,<br>
Mike<br>
<br>
* - Dang, I forgot to add support for OO interfaces into the customer<br>
connection suggestions!</font>
<br><font size=3><br>
<br>
On Fri, May 8, 2015 5:23 pm, Florin Wach (SI) wrote:<br>
> Hi Mike,<br>
><br>
> as I'm on the train, here's the short version after having thought
about<br>
> some alternatives:<br>
><br>
> Instead of a Wait step, create a subflow with a single asynchronous<br>
> background step that executes a dummy method.<br>
><br>
> Within that step you create a container element that is bound to the
name<br>
> of the dynamic event you're waiting for.<br>
><br>
> As terminating events of that task you define once all the possible<br>
> events.<br>
><br>
> A instance linkage check FM now compares the name of the event with
the<br>
> value of that container element of the task.<br>
><br>
> Have a look at the instance binding of BUS2012.Released where the
element<br>
> 'ReleaseCode' is compared.<br>
><br>
> The subflow has only the reason to avoid 20+ outcomes of the task
. With<br>
> a subflow it looks more cleaner.<br>
><br>
><br>
> Mit freundlichen Gruessen / With kind regards<br>
> Florin Wach<br>
> Senior Workflow Engineer<br>
> Systems-Integration<br>
><br>
> --------------------------------------------------<br>
> </font><a href="http://www.systems-integration.net/" target=_blank><font size=3 color=blue><u>http://www.systems-integration.net</u></font></a><font size=3><br>
><br>
>> Am 08.05.2015 um 18:01 schrieb Mike Pokraka<br>
>> <</font><a href=mailto:wug@workflowconnections.com><font size=3 color=blue><u>wug@workflowconnections.com</u></font></a><font size=3>>:<br>
>><br>
>> Hi all,<br>
>><br>
>> I bumped into a limitation in the wait step and was wondering
if anyone<br>
>> had any more elegant workarounds than my klutzy attempts:<br>
>><br>
>> What I'd like to do is wait for a dynamic event. It would be easy
with a<br>
>> container element for the event name, but unfortunately the Wait
step<br>
>> complains that "Event &WAITFORTHIS& does not exist"
when I try to insert<br>
>> a<br>
>> container element into the event field of a wait step.<br>
>><br>
>> Background:<br>
>> The WF can be started by a variety of events. Depending on triggering<br>
>> event, there will be a variety of different events to wait for.<br>
>><br>
>> Some approaches I've considered are:<br>
>> 1. A bunch of parallel wait branches and a series of switches
to<br>
>> de/activate them, but that's nasty (20+ events).<br>
>> 2. The start event triggers a second workflow (one for each scenario),<br>
>> which only waits for the relevant reactors and then signals the
main WF<br>
>> with a secondary event. Ugly.<br>
>> 3. Custom event receiver module in the event linkage table to
manipulate<br>
>> the relevant workflow. Obscure.<br>
>><br>
>> I can't help thinking there must be a better way :-)<br>
>><br>
>> Any input appreciated,<br>
>> Mike<br>
>> (Cross-posted on WUG and SCN)<br>
>><br>
>> _______________________________________________<br>
>> SAP-WUG mailing list<br>
>> </font><a href="mailto:SAP-WUG@mit.edu"><font size=3 color=blue><u>SAP-WUG@mit.edu</u></font></a><font size=3><br>
>> </font><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target=_blank><font size=3 color=blue><u>http://mailman.mit.edu/mailman/listinfo/sap-wug</u></font></a><font size=3><br>
><br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> </font><a href="mailto:SAP-WUG@mit.edu"><font size=3 color=blue><u>SAP-WUG@mit.edu</u></font></a><font size=3><br>
> </font><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target=_blank><font size=3 color=blue><u>http://mailman.mit.edu/mailman/listinfo/sap-wug</u></font></a><font size=3><br>
><br>
<br>
_______________________________________________<br>
SAP-WUG mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:SAP-WUG@mit.edu"><font size=3 color=blue><u>SAP-WUG@mit.edu</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target=_blank><font size=3 color=blue><u>http://mailman.mit.edu/mailman/listinfo/sap-wug</u></font></a>
<br>
<br><font size=3>_______________________________________________<br>
SAP-WUG mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:SAP-WUG@mit.edu"><font size=3 color=blue><u>SAP-WUG@mit.edu</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><font size=3 color=blue><u>http://mailman.mit.edu/mailman/listinfo/sap-wug</u></font></a><tt><font size=2>_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
</font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
</font></tt>
<br><font size=2 face="sans-serif"><br>
Unless stated otherwise above:<br>
IBM United Kingdom Limited - Registered in England and Wales with number
741598. <br>
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU<br>
</font>