Synchronous Dialog Chains and the UWL

[Hilsbos, Margaret A]

Greg,
 
If I understand your question, the only problem with your solution is that the user sees the update tasks in their UWL until the program runs.
 
Is it possible to change your UWL configuration so that work items for that task number just aren't displayed in the UWL? I played with the UWL awhile back (we ended up not using it for that project), but I seem to remember having trouble with certain tasks not showing up until I 'fixed" something in the config file for the task. Seems you ought to be able to use what was my problem, for your solution. 
 
Sorry I can't give a more detailed suggestion but thought I'd throw this out there, and maybe someone more experienced with UWL can confirm whether this is true and if so, what you need to do.
 
Margaret Hilsbos
Day & Zimmermann

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf Of Gregory Utley
Sent: Thursday, August 11, 2005 4:50 PM
To: sap-wug at mit.edu
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

 

 

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