UWL SWFVISU WebDynpro - application as paramater

[Robert van den Berg]

Jocelyn, all,



I have a container element with the correct webdynpro application
(and/or URL).

I also have a containerelement with a parameter for the caseID for which
the task is concerned.



So I want to call the WebDynproLaucher with the correct application and
also pass the parameter so the data from the backend can be retrieved
within the WebDynpro application.



I thought maybe it is possible to change the UWL XML so the value for
the WebDynproLaucher is a variable?



For example (with CONTAINER_ELEMENT_URL and caseID):



<ItemType name="uwl.task.webflow.TS99900078"
connector="WebFlowConnector"

defaultView="DefaultView" defaultAction="launchWebDynPro"

executionMode="default">

<ItemTypeCriteria externalType="TS99900078"
connector="WebFlowConnector"/>

<Actions>

<Action name="launchWebDynPro" handler="SAPWebDynproLauncher">

<Properties>

<Property name="WebDynproApplication"
value="${item.CONTAINER_ELEMENT_URL}"/>

<Property name="WebDynproDeployableObject" value="sap.com/tc~wd~tools"/>

<Property name="System" value="SAP_LocalSystem"/>

<Property name="caseID" value="${item.caseID}" />

</Properties>

</Action>

</Actions>

</ItemType>





Other possibilities:

- call the WebDynpro from the method in de task. So then the XML in the
UWL must be a tasklauncher in the back-end. But how can I call a
WebDynpro from ABAP (with a parameter)?

- or call the iView URL direct from the backend. So then the task in the
UWL must be a tasklauncher in the back-end. But how can I call a URL
from the UWL via a workflow task/method?



Regards,

Robert

On Jul 3, 2013 09:21 "Dart, Jocelyn" <jocelyn.dart at sap.com> wrote:

> 
> Hi Robert,
> 
> You can pass whatever parameters you need to DYNPARAM but that’s
> usually
> for the parameters passed to the application itself.
> 
> The difficulty might be in getting the UWL to launch the correct
> application, but its theoretically possible. An alternative is to pass
> it as a container element of the task.
> 
> Remember SWFVISU is only used to generate the UWL XML file entry – you
> can always override it in your custom UWL XML file.
> 
> 
> 
> Give it a go but I don’t promise anything.
> 
> 
> 
> Just thinking an alternative may to be to use a Task Expression to
> solve
> the problem – i.e. have a task for each application but use the Task
> Expression field on the workflow step to default in the correct task
> for
> the correct application using a workflow container element. Then your
> SWFVISU would still have 7 different tasks, but your workflow would
> only
> have one task at design time.
> 
> Just a thought… as that’s how I would approach it personally… i.e.
> work
> with the existing functionality rather than counter to it.
> 
> Up to you though…..
> 
> Regards,
> 
> Jocelyn
> 
> 
> 
> From:sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
> Behalf
> OfRobert van den Berg
> Sent: Tuesday, 2 July 2013 5:07 PM
> To: SAP Workflow Users' Group
> Subject: SWFVISU WebDynpro - application as paramater
> 
> 
> 
> All,
> 
> 
> 
> We have an application where we have 1 workflow task in de UWL which
> we
> want to be used for 7 WebDynpro applications. In the workflow, I can
> determine the correct webdynpro application.
> 
> 
> 
> Is it possible to pass the application as a paramater? So the setting
> "APPLICATION" inSWFVISU with the type WebDynpro ABAP?
> 
> 
> 
> Or should I use an iView and let the method call the URL? And if that
> is
> the solution: how can I pass a parameter to the iView? Using DYNPARAM?
> 
> 
> 
> Kind regards,
> 
> Robert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20130704/9cb02721/attachment.htm