Create event via status management

[Dart, Jocelyn]

Hi Patrick,
Just because you have one event per user status does not mean you need a workflow for each event.
When you assign multiple triggering events the workflow is started for ANY of those events - i.e. a logical "or" approach is used.
 
So approach is:
1. Use one event per user status
2. Add all events as triggering events of the same workflow
3. Use _EVT_NAME in the workflow/event binding to capture which event was used.
 
 
If you also allow adhoc direct start of the workflow then your event name is empty, so you can test fot direct start as well.
Jocelyn
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of de Valensart Schoenmaeckers, Patrick
Sent: Tuesday,8 June 2004 9:49 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Create event via status management
 
 
Mike,
 
Probably my brain cells were too tired yesterday evening to think about
binding _EVT_NAME to a workflow container element... Thanks for the tip!
 
I also thought about adding an attribute to my ZBUS2032 subtype, but that
wouldn't have solved the issue because several statuses can co-exist
together in a sales order and there is no way to know which one relates to
the workflow instance calling the attribute.
 
Cheers,
Patrick
 
-----Original Message-----
From: Michael Pokraka [mailto:workflow at quirky.me.uk]
Sent: Monday, June 07, 2004 7:13 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Create event via status management
 
Hi Patrick,
Bind _EVT_NAME into a WF element 'TriggeringEvent'.
A slight downside is for manually started flows (e.g. admin restart or
whatever).
Another option is to add an attribute for the status to a ZBUS2032 subtype
and check that in your flow.
Cheers
Mike
 
de Valensart Schoenmaeckers, Patrick wrote:
> Hi.
>
> I need to trigger a workflow every time a user status is set on a sales
> order. Until here, nothing difficult (I create my event via status
> management - transaction BSVZ - and restrict it to the relevant user
> statuses. Then I use that event as a triggering event of my workflow).
>
> The issue arises when at some stage of my workflow I need to know which
> status triggered it. The only solution I could find until now is to have
one
> event for each possible status. But that doesn't solve the problem because
> there is no possibility (that I am aware of) to know which one of the
> various triggering events actually started the workflow. Thus I also need
to
> have one workflow per event. This is definitely not nice as all workflows
> would be almost identical anyway and it increases the maintenance cost.
>
> Anybody has a better solution to offer? I also thought about defining each
> of my events with a parameter "Status", and then use a check function
module
> to fill-in the event container, but that seems tricky. Anyone already
tried
> to do that?
>
> Thank you all in advance for your replies.
>
> Cheers,
>
> Patrick
>
>