<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head></head><body style="font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;">Hmm.. I have the URL and/or Application as a container element in the task. So I could use it both as a container element or with the DYNPARAM.<div><br></div><div>Where can I find documentation about how to configure SWFVISU? Because it is very unclear to me and I can't find any documentation on it. All documentation is about the portal part, not the workflow part or the SWFVISU part.</div><div><br></div><div>Kind regards,</div><div>Robert<br><br><p>On Jul 3, 2013 09:21 "Dart, Jocelyn" <a href="mailto:jocelyn.dart@sap.com"><jocelyn.dart@sap.com></a> wrote:</p><blockquote type="cite"> <br>Hi Robert,<br><br>You can pass whatever parameters you need to DYNPARAM but that’s usually<br>for the parameters passed to the application itself.<br><br>The difficulty might be in getting the UWL to launch the correct<br>application, but its theoretically possible. An alternative is to pass<br>it as a container element of the task.<br><br>Remember SWFVISU is only used to generate the UWL XML file entry – you<br>can always override it in your custom UWL XML file.<br><br><br><br>Give it a go but I don’t promise anything.<br><br><br><br>Just thinking an alternative may to be to use a Task Expression to solve<br>the problem – i.e. have a task for each application but use the Task<br>Expression field on the workflow step to default in the correct task for<br>the correct application using a workflow container element. Then your<br>SWFVISU would still have 7 different tasks, but your workflow would only<br>have one task at design time.<br><br>Just a thought… as that’s how I would approach it personally… i.e. work<br>with the existing functionality rather than counter to it.<br><br>Up to you though…..<br><br>Regards,<br><br>Jocelyn<br><br><br><br>From:sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<br>OfRobert van den Berg<br>Sent: Tuesday, 2 July 2013 5:07 PM<br>To: SAP Workflow Users' Group<br>Subject: SWFVISU WebDynpro - application as paramater<br><br><br><br>All,<br><br><br><br>We have an application where we have 1 workflow task in de UWL which we<br>want to be used for 7 WebDynpro applications. In the workflow, I can<br>determine the correct webdynpro application.<br><br><br><br>Is it possible to pass the application as a paramater? So the setting<br>"APPLICATION" inSWFVISU with the type WebDynpro ABAP?<br><br><br><br>Or should I use an iView and let the method call the URL? And if that is<br>the solution: how can I pass a parameter to the iView? Using DYNPARAM?<br><br><br><br>Kind regards,<br><br>Robert</blockquote></div></body></html>