How to integrate a BSP in a workflow step?

Wed Apr 18 03:36:43 EDT 2007

Hi Serge,

Thanks a lot for your explanation. But that is exactly what I would do if 
there wasn't the constraint to have dynamic urls. To recap the issue:
- I have several bsp's. 
- My workflow has a background step with a method that determines the bsp 
to be called at each step and send emails accordingly. 
- I want to modify that step so that the correct bsp url is returned in a 
container element (instead of being sent out by email) and then have an 
asynchronous step from which my bsp is executed.
But if I use the swfvisu mechanism it will always point to the same url, 
right?

Thanks anyway and kind regards,
Patrick

----- Message from "Breslavets Sergey" <sergey.breslavets at volvo.com> on 
Tue, 17 Apr 2007 12:54:46 -0400 -----
To:
"SAP Workflow Users' Group" <sap-wug at mit.edu>
Subject:
RE: How to integrate a BSP in a workflow step?
Hi Patric,

you can generate an iview from your bsp and then setup the visualization 
(SWFVISU) for the task to point to the PCD location for the iview, then 
re-register workitems for uwl (function in the portal system admin). After 
that your bsp should start automatically when you execute your workitem 
from UWL.

do you plan to run the workitems from sapgui as well? there are different 
way the workitem is executed from uwl and from sapgui inbox. if you plan 
to use sapgui inbox as well then you'd need to have your task method to 
call your bsp and take care of sso. 

also, your bsp application has to handle all the workitem operations 
(lock, unlock, complete, etc.) 

hope this help,
Serge

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf 
Of patrick.j.de-valensart at gskbio.com
Sent: Tuesday, April 17, 2007 11:38 AM
To: sap-wug at mit.edu
Subject: How to integrate a BSP in a workflow step?

Hi wug'ers, 

I have an old custom workflow used for access request approval. That 
workflow has a rather uncommon logic: it is first sending out a variable 
number of emails (through a custom method) each containing dynamically 
generated url (the same custom method is generating the url's) pointing to 
custom BSP's. It is then followed by a wait for event step, and the 
expected event is generated by the BSP's when they are executed by the 
users who received the emails. 

Now we are implementing UWL, but we do not want to integrate emails in it. 
Therefore I need to have this workflow generating workitems instead of 
sending emails. The workitems must call the BSP's dynamically (the url 
could be contained in a container element for example), and must be 
asynchronous so that they can terminate with the events published by the 
BSP's. What would be the best way to achieve this? I tried with webforms 
and web service steps, but this is where I am starting to get lost... 

Any help or tip on this will be greatly appreciated... 

Thanks a lot, 
Patrick 

The information contained in this message is confidential and is intended for the addressee(s) only.  This information may also be legally privileged.  If you have received this message in error or there are any problems please notify the originator immediately.  The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden.  GlaxoSmithKline Biologicals will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on.

L'information contenue dans ce message est confidentielle et dediee exclusivement au(x) destinataire(s). Cette information peut egalement etre de nature legalement privilegiee. Si vous avez recu ce message par erreur ou s'il y a un probleme, priere d'en avertir l'expediteur immediatement.  L'usage illicite, la divulgation, la copie ou la modification de ce message sont strictement interdits.  GlaxoSmithKline Biologicals ne peut etre tenue responsable des dommages directs, speciaux, indirects ou consecutifs resultant de la modification du contenu du message par un tiers ou d'un virus transmis avec le message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20070418/9f9232be/attachment.htm