SAP_WAPI_WORKITEM_COMPLETE versus asynchronous steps

[Dart, Jocelyn]

Hi Carolyn,

No - there are many good and valid reasons for using asynchronous
methods vs. synchronous methods - it's not a lesser approach or an
outmoded approach. 
A terminating event is often the best way of knowing your changes are
really complete - especially if those changes have been applied in an
update task controlled logical unit of work - i.e. separate to the
dialog transaction itself. 

SAP_WAPI_WORKITEM_COMPLETE is there to handle situations where you need
to create special handling - e.g. for mass handling of work items, or to
add extra features to UWL work items.   

Think of it this way: You may never need to use the WAPI but you will
definitely still use asynchronous tasks. 

Regards,
Jocelyn 

-----Original Message-----
From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] On Behalf
Of Carolyn Fuller
Sent: Friday, 20 February 2009 10:40 AM
To: SAP Workflow Users' Group
Subject: SAP_WAPI_WORKITEM_COMPLETE versus asynchronous steps

Hi,

Under 4.6c if I had a need for a dialog step to be completed outside  
of the SAPGui Inbox, I used an asynchronous method and triggered the  
necessary terminating event from the custom code. Can I now, instead,  
use a synchronous method and call SAP_WAPI_WORKITEM_COMPLETE from the  
custom code? Does this RFC replace the need to use asynchronous  
methods when working outside of the Gui Inbox?

---
Carolyn Fuller
Massachusetts Institute of Technology
Information Services and Technology
Administrative Computing
Senior Analyst/ Programmer
(617) 253-6213
http://fuller.mit.edu/

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug