UWL SWFVISU WebDynpro - application as paramater

[Dart, Jocelyn]

Hi Robert,
Separate with ampersand - & or &
Also the attributes usually match to custom attributes of the item so they would be ${item.ZSFNUMMER} for example
Regards,
Jocelyn

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Robert van den Berg
Sent: Wednesday, 10 July 2013 5:30 PM
To: SAP Workflow Users' Group; SAP Workflow Users' Group
Cc: SAP Workflow Users' Group
Subject: Re: UWL SWFVISU WebDynpro - application as paramater

Jocelyn, (and others)

how can I pass >1 dynamic parameters?

do I seperate them by a comma?
For instance: ZSFNUMMER=${ZSFNUMMER}, URL=${URL}, APP=${APPLICATIE}

Or is this not possible?

On Jul 4, 2013 11:08 "Dart, Jocelyn" <jocelyn.dart at sap.com><mailto:jocelyn.dart at sap.com> wrote:

Hi Robert

Please look again at my suggested alternative if you can't get your
preferred option working (but by all means try that first - it looks
plausible).




You really do *not* want to call the wda or iview in a method. We have
seen a number of sites try this and it leads to all sorts of unfortunate
side effects particularly around web browser sessions.


Task expressions are very easy to use and a great technique to add to
your collection

Rgds

Jocelyn
Sent from my iPhone with many apologies for the spelling, grammar and
any other deficiencies


On 04/07/2013, at 6:54 PM, "Robert van den Berg " <<wug at bergtop-ict.nl<mailto:wug at bergtop-ict.nl>>>
wrote:



> 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="http://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><mailto: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:wug-bounces at mit.edu>> [mailto:sap-wug-bounces at mit.edu
> > <sap-wug-bounces at mit.edu><mailto:sap-wug-bounces at mit.edu%0b%3e%20%3e%20%3csap-wug-bounces at mit.edu%3e>] 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

> _______________________________________________
> SAP-WUG mailing list
> <SAP-WUG at mit.edu><mailto:SAP-WUG at mit.edu>
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20130717/69e80268/attachment.htm