Question on WebFlow

[Rickayzen, Alan]

Natasha,
It depends on the release of the Portal (SAP EP 6?) and the release of
the workflow SAP Web AS (6.20?).
 
The simplest and most elegant method (if you have a sufficiently recent
release) is to use the documention described in the SAP NetWeaver '04
online help
 
<http://help.sap.com/saphelp_nw04/helpdata/en/59/d516690e854c7090ae15bf4
92a869f/frameset.htm> 

Scroll down until you find:

"Business Workflow Task Launch Customization Alternatives"

Here you will see swfvisu described (but call this transaction first in
your system to check that your release is recent enough).

If you can use this technique you don't need to follow steps 1,2 and 4.
Otherwise use Mark's method.

You may ask yourself why this appears so complicated. The simple answer
is that SAP could have enabled you to use this feature only for business
suite applications built on SAP NetWeaver '04 (simple configuration).
However, SAP decided to make the Universal Worklist available to older
business suite applications as well so there are different enabling
techniques depending on the release of the different software
components.

Best regards,
Alan Rickayzen




________________________________

	From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]
On Behalf Of Baunach, Natasha R
	Sent: Mittwoch, 11. Mai 2005 19:45
	To: SAP Workflow Users' Group
	Subject: RE: Question on WebFlow
	
	

	Alan,

	I am using enterprise portals...  Are these the steps I need to
do?

	1.	Customize in WF_HANDCUST 
	2.	Create BSP with at the end raises terminating event 
	3.	Create webflow service in WF_EXTSRV 
	4.	Generate my task as the last step in WF_EXTSRV 
	5.	Insert task into my workflow definition (with
terminating event) 

	 

	At point what does transaction SWFVISU come into play?  Or do I
use it instead of the steps above?

	 

	Thanks,

	Natasha

	 

	________________________________

		From: sap-wug-bounces at mit.edu
[mailto:sap-wug-bounces at mit.edu] On Behalf Of Rickayzen, Alan
	Sent: Wednesday, May 11, 2005 5:25 AM
	To: SAP Workflow Users' Group
	Subject: RE: Question on WebFlow

	 

	Natasha,

	If you're using the universal worklist in SAP Enterprise Portals
as your inbox it's even easier. 

	You simply configure the task using the swfvisu transaction in
your backend and make sure that your bsp completes with a terminating
event (i.e. an asynchronous task where you program the terminating event
into your bsp).

	 

	BTW, the java launch handler mentioned in the SAP insider
article was only a temporary solution and is now no longer needed.

	 

	Best regards,

	Alan Rickayzen

		 

		________________________________

				From: sap-wug-bounces at mit.edu
[mailto:sap-wug-bounces at mit.edu] On Behalf Of Griffiths, Mark
		Sent: Mittwoch, 11. Mai 2005 13:13
		To: SAP Workflow Users' Group
		Subject: RE: Question on WebFlow

		This is all covered in BIT603 - if you can get someone
to pay for you to go on the course you would find it very useful!

		 

		In a nutshell:

		- customise in WF_HANDCUST

		- set up anonymous dialog user in SICF for the wshandler
service

		- Create a BSP including coding for a callback URL (see
BSPs SWXTRA* for examples) and parameters

		- Create a webflow service in WF_EXTSRV for your BSP
including the parameters

		- Generate your Task

		- Insert the task in your workflow

		 

		Easy!

		 

		Hope this helps,

		 

		Regards,

		 

		Mark

		 

		SAP UK

		 

			-----Original Message-----
			From: sap-wug-bounces at mit.edu
[mailto:sap-wug-bounces at mit.edu] On Behalf Of Baunach, Natasha R
			Sent: 11 May 2005 02:30
			To: SAP-WUG at mit.edu
			Subject: Question on WebFlow

			Dear user group,

			 

			I am trying to create a simple workflow that
would call a BSP in a dialog step and then after some action on BSP, say
button push, return to the workflow and complete the workitem.  I am not
100% sure what config to populate in transaction WF_EXTSRV.  I cannot
find any documentation on this and haven't done this type of workflow
activity before.  Any help would be much appreciated.

			 

			Thanks,
			Natasha