Synchronous Dialog Chains and the UWL

[Gregory Utley]

Jeff,

 

Thanks for the suggestion.  The problem with a secondary method is that
its execution is not dependent upon the outcome of the task method; it
always executes.  The trip can be approved, rejected, or sent back for
corrections, and the travel object's APPROVE method would be executed in
any case.

 

Thanks,

Greg Utley

CiTR!X Systems, Inc.

SAP Development Team

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Jeff Rappaport
Sent: Friday, August 12, 2005 1:00 PM
To: SAP Workflow Users' Group
Subject: Re: Synchronous Dialog Chains and the UWL

 

Gregory,

 

   Could you take the 2nd step Method & move it into the 1st Step as an
After execution Secondary Method?

 

Jeffrey A. Rappaport
Business Workflow, LLC
Voice: (732) 355-0123
Fax:    (509) 757-4144
Email: Jeff at Business-Workflow.com
Web:  www.Business-Workflow.com

	----- Original Message ----- 

	From: Gregory Utley <mailto:Gregory.Utley at citrix.com>  

	To: sap-wug at mit.edu 

	Sent: Thursday, August 11, 2005 4:49 PM

	Subject: Synchronous Dialog Chains and the UWL

	 

	All,

	 

	A question to all:  We are soon implementing the SAP Portal.
For the most part, we've had no problems with workflow applications in
the portal environment, and the consolidation of agent approval
notifications in the UWL is an improvement over using system dependent
SBWP inboxes.

	 

	The one major downside for workflow in the portal (specifically
the UWL) is the loss of "synchronous dialog chain" processing (OSS Notes
794439 and 487649).  The standard SAP travel expense workflow depends
upon a two-step approval process (approve, then update the employee
master) via workflow.  With the loss of synchronous dialog processing,
the "update" step goes into READY status in the UWL instead of just
executing automatically as it did before.  The bottom line: the approver
must approve twice.

	 

	I wrote a program that will run periodically in background to
identify these READY update tasks and trigger them.  This solves the
problem (the approver only approves once), but it's not an optimum
solution since it leaves the update task in the approver's UWL inbox
until the background program runs.

	 

	If anyone else has run into this problem and solved it in a more
efficient way, I'd love to hear from you.

	 

	Greg Utley

	CiTR!X Systems, Inc.

	SAP Development Team

	 

	 

	
________________________________


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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050812/d0228c27/attachment.htm