‎2007 May 18 6:40 PM
I have a workflow that seems to be getting caught in the 'race between the update task and the WebtFlow Engine' - per the book 'Practical Workflow for SAP'.
One suggested resolution for this was to create an event that trigger the next step once the update has taken place.
I have tried creating a Terminating Event and right now I am trying a Triggering Event.
I have Step A - this is a background step to determine an agent and put that agent in the WF container and to update a table with that value. After the commit work for the update, I put my code to call the function to create the event UPDATED in my custom BO.
The second step - Step B is a dialog step but has a triggering event defined as the UPDATED event from the same BO.
A couple of questions:
1. When executing this workflow, is it possilbe for me (via SWIA) to see if my event was created successfully?
2. I have done an event trace and it appears that the event is created and the receiving event is triggered.
3. In SWIA, it appears that the WF is executing as designed (but not knowing whether the triggering event caused the second step to execute or not).
In order to test the triggering event, I left the triggering event condition on Step B, but in Step A, I commented the code to trigger the UPDATED event - thinking this would cause Step B to not process..... but it still does.
Something is not working properly and I cannot figure it out.
Any help would be appreciated.
Thanks.
‎2007 May 20 5:43 PM
You can try creating another workflow for second step and keep the triggering event for this new workflow as Update on the BO.