Purchase Requisition Workflow - Editing after Rejection

[Pokraka, Michael]

Ummm, how exactly is the 'restart' triggered? Do you explicitly start it
from the original WF?
 
If so, Jose's suggestion is the way to go.
Another alternative is to simply send the Edit task and end the original WF
there. The second WF should be triggered by a BUS2009.SIGNIFICANTLYCHANGED
event.
 
Cheers
Mike
 
-----Original Message-----
From: Abby Dywan [mailto:abby.dywan at us.ibm.com]
Sent: 30 October 2002 14:30
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Purchase Requisition Workflow - Editing after Rejection
 
 
Hi all -
 
We have modified the standard purchase requisition workflow to send the
purchase requisition back to the creator after rejection.  When the creator
opens the purchase requisition and makes changes, the workflow should
re-start.
 
We have this situation working except for one problem.  When the creator
opens the purch req and simply closes out of it again - without saving,
without making any changes at all - the workflow re-starts anyway.  I think
this has to do with the method for the business object BUS2009.Edit being
synchronous, but I can't seem to think of a way around it.  How can I fix
it so that the workflow only re-starts when changes have been made?
 
Any suggestions would be appreciated - thanks!
 
Abby  :)
 
------------------------------------------------------------------------------
This e-mail is intended for the use of the addressee(s) only and may contain privileged, confidential, or proprietary information that is exempt from disclosure under law.  If you have received this message in error, please inform us promptly by reply e-mail, then delete the e-mail and destroy any printed copy.   Thank you.
 
 =============================================================================