on 03-24-2010 11:16 AM
Hi all,
I would like to know if there is a way of identifying which triggering event started the wf.
The situation is like this: i have a workflow that can be started by one of 6 triggering events (6 different situations for vendor master data - creation needed, extension needed, change needed and so on). I have to do different steps inside the workflow function of which event actually triggered the wf.
Is there a container element that gets some sort of identification for the event that actually triggered the wf?
I found a container element that holds the name of the event but it's a multiline container element (so i guess it holds all the event names) and i can't use it in a multiple condition.
Thank you
Cristina
Very simple. Create a Workflow Container element FLAG_EVENT of type BOOLE-BOOLE. This field should be set binded with 'X' from event to Workflow when a particular event is triggered in the binding from event to Workflow. Later on in your Workflow design check for this Flag. If this is set the event is for which you set the Flag.
Thanks
Arghadip
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kristof,
this is what i thought also...to create a parameter for each event and assign a constant to it (a letter for instance).
But i can create event parameter as object type or ABAP dictionary and i can't assign initial value...or at least, if there is a way to do this, i don't know it.
Thanks
Cristina
for those events, you can add want you want as abap dictionary
it doesn't matter, just look in SE11, where you can find any kind of data element of type char1 and use that one.
Those events, are those standard events or events that you trigger yourself with the function SWE_EVENT_CREATE?
Edited by: Kristof De Bruecker on Mar 24, 2010 2:56 PM
Kristof, Cristina,
You are on the right track but you don't even need to fill something in the event container. Just create a container element in your workflow container as advised by Arghadip, but choose a multiple value data element (i.e. one letter per even as you suggested) instead of a bollean. You can then fill that container element in the event->workflow binding by hardcoding the letter.
Rgds,
Patrick
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.