Invalid WDA item link generated from Extended Notifications

Tue Nov 29 09:15:40 EST 2011

Jocelyn. 

I was thinking about the same. Will plan doing it soon. 

Thank you.
Baba

--- On Mon, 11/28/11, Dart, Jocelyn <jocelyn.dart at sap.com> wrote:

From: Dart, Jocelyn <jocelyn.dart at sap.com>
Subject: RE: Invalid WDA item link generated from Extended Notifications
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Date: Monday, November 28, 2011, 5:10 PM

Great news Baba! Glad you got it working. 
You know picking up a WDconfig id for extended notifications is something that would be useful for many folk...perhaps you could write a quick blog about that on SDN?
Just a thought
Regards,
Jocelyn 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Baba Jammi
Sent: Tuesday, 29 November 2011 8:54 AM
To: SAP Workflow Users' Group
Subject: RE: Invalid WDA item link generated from Extended Notifications

Jocelyn, 

It worked !!!

I was able launch Web dynpro using extended notifications URL. I changed SWFVISU parameters to pass ConfigId of the Web Dynpro and WI_ID instead of Item_RequestID as per your suggestion. 

Thank you so much for your valuable suggestions and appreciate your patience in guiding me. 

Regards,

Baba

--- On Thu, 11/24/11, Dart, Jocelyn <jocelyn.dart at sap.com> wrote:

From: Dart, Jocelyn <jocelyn.dart at sap.com>
Subject: RE: Invalid WDA item link generated from Extended Notifications
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Date: Thursday, November 24, 2011, 5:57 PM

Hi Baba, 
There’s a standard parameter for passing across the WD configuration id to WD applications.  
The quickest way to get this accurately is to use SE80 to test your application starting from that WD configuration... i.e. using the context menu on the WD configuration entry in SE80. 
Once you know that you can include it in the Dynamic Parameters of SWFVISU. 

However if you are just doing extended notifications ... then your LRF_REQUEST_ID parameter won’t work on its own as to add REQUEST_ID to the “item” object would involve running it through UWL config. 

This is a standard application surely going by the name?  It should be just using WI_ID and the Wd configuration ... and then deriving the request id inside the application based on the WI_ID? 
Or have you enhanced the application is some way to use LRF_REQUEST_ID?
Regards,
Jocelyn  

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Baba Jammi
Sent: Friday, 25 November 2011 5:14 AM
To: SAP Workflow Users' Group
Subject: Re: Invalid WDA item link generated from Extended Notifications

Thank you Jocelyn for so detailed suggestion. 

As you said, I am trying to launch application from the URL generated from extended notifications without worrying about UWL configuration. I am thinking we are missing Web Dynpro Configuration id from the URL. I am not sure how we can pass this. I also gone thru online documentation, every where it talks about the configuration I'd of the web dynpro along with dynpro parameters. 

I will do more research as per your below email and get back. Thank you again for all the help.

Regards,

Baba

On Nov 23, 2011, at 5:45 PM, "Dart, Jocelyn" <jocelyn.dart at sap.com> wrote:

Hi Baba, 
Doesn’t look like you’ve figured out the correct URL yet.  If the URL you are calling doesn’t work there’s no point worrying about the UWL configuration yet. 
You need to make sure you can call the URL directly and get the correct response first.

If you can’t call the URL directly and get the correct response from the application you need to sort out what actually needs to be in that URL before you worry about what the UWL is generating. 
Perhaps you are missing another parameter, or your user isn’t a recipient of that work item or lacking some auth or something.  As this is a standard application, your best option maybe to search the SAP Library help for more clues.   

You should also check whether there is a standard UWL Configuration file provided for that application as part of the matching Portal Business Package  ... if you can find an equivalent standard task that would help you work out what you are missing in the UWL configuration.  You might also want to get a copy of Darren Hague’s SAP Press book on the UWL to help you understand how to configure the UWL file, once you have sorted out the URL. 

Regards,
Jocelyn 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Baba Jammi
Sent: Thursday, 24 November 2011 1:45 AM
To: SAP Workflow Users' Group
Subject: RE: Invalid WDA item link generated from Extended Notifications

Hi Jocelyn,

I would prefer to use a dynamic value rather than using LRF_REQUEST_ID=A. 

I tried replacing %7bitem.REQUESTID%7d in URL with actual Request ID and page is still not loading correctly. It just loads the header of the webdynpro. I am attaching the screenshot to this email. 

I am guessing we may have to pass the configuration name also when we call the application. If yes, how can I pass the web dynpro configuration HRESS_AC_PTARQ_LEAVREQ in the URL when we call the application hress_a_ptarq_leavreq_appl ? 

Thank you,

Baba

--- On Tue, 11/22/11, Dart, Jocelyn <jocelyn.dart at sap.com> wrote:

From: Dart, Jocelyn <jocelyn.dart at sap.com>
Subject: RE: Invalid WDA item link generated from Extended Notifications
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Date: Tuesday, November 22, 2011, 5:35 PM

Hi Baba,
Do you literally want LRF_REQUEST_ID=’A’ or do you want a dynamic value ?

If you literally want the constant just correct your SWFVISU entry.
If you want to pass a dynamic value you’ll need to work out what container element of your task holds the value and then adjust the ItemType tag to include the relevant CustomAttributes for your UWL config XML file. 

Before you do either of those ... suggest you take the URL, replace %24%7bitem.REQUESTID%7d with the real  value you want to use, and check that the application launches correctly. 
This is so that you confirm there aren’t any other problems happening such as security/auth issues. 

Regards,
Jocelyn 

From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] On Behalf Of Baba Jammi
Sent: Wednesday, 23 November 2011 5:44 AM
To: SAP Workflow Users' Group
Subject: RE: Invalid WDA item link generated from Extended Notifications

Thank you Jocelyn.

I am one step ahed now. I am able to get a valid link as below after I added NAMESPACE = SAP in SWFVISU configuration.

http://---.--.com:1081/sap/bc/webdynpro/SAP/hress_a_ptarq_leavreq_appl?WI_ID=000000436181&LRF_REQUEST_ID=%24%7bitem.REQUESTID%7d&sap-system-login-basic_auth=X&sap-client=011&sap-language=EN

When I click the above link, application hress_a_ptarq_leavreq_appl still not launched correctly. I am attaching a screenshot.

How can I call application hress_a_ptarq_leavreq_appl with configuration name HRESS_AC_PTARQ_LEAVREQ with Paraments LRF_REQUEST_ID = 'A' from the link?

Thank you,

Baba

--- On Tue, 11/22/11, Dart, Jocelyn <jocelyn.dart at sap.com> wrote:

From: Dart, Jocelyn <jocelyn.dart at sap.com>
Subject: RE: Invalid WDA item link generated from Extended Notifications
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Date: Tuesday, November 22, 2011, 1:53 AM

Hi Baba, 
It still doesn’t sound like you have extracted the actual URL that has been generated in the email?
You should be able to see in the URL itself in the actual email whether or not the value is there.   Maybe try right clicking on it in the generated mail itself and using Edit Hyperlink or similar to get to the URL. 

Also if you are using item.RequestId there should be a CustomAttributes tag for Request Id in the ItemType tag that matches your task in your UWL configuration file. 
Otherwise the UWL won’t know how to source the value for RequestId.   
Regards, 
Jocelyn 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Baba Jammi
Sent: Tuesday, 22 November 2011 1:05 PM
To: SAP Workflow Users' Group
Subject: RE: Invalid WDA item link generated from Extended Notifications

Jocelyn,

Thank you for you response. 

1. Yes, I did confirm the URL by executing WDA from SE80.

2. I did confirm there are no double // after webdynpro.

3. Can you please tell me little more, how can I confirm item.Requestid is returning a value in the URL? When I click the URL, i do get an JAVA SCRIPT error, nothing else happens.  To me it looks like a dummy URL. 

What attributes do I need to check in the custom task?

Thank you,

Baba

--- On Mon, 11/21/11, Dart, Jocelyn <jocelyn.dart at sap.com> wrote:

From: Dart, Jocelyn <jocelyn.dart at sap.com>
Subject: RE: Invalid WDA item link generated from Extended Notifications
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Date: Monday, November 21, 2011, 5:23 PM 

Hi Baba, 
First get the exact URL that has been generated – e.g. by clicking on it and seeing what comes up in the web browser.
Check: 
1.       Host and port are correct for your WDA system.... if in doubt, try testing the WDA from SE80 – that should generate an equivalent URL to check against. 
2.       Check you don’t have a double slash // in the URL after webdynpro ... you might need to remove that last slash. 
3.       Check item.REQUESTID is returning a value in the URL that has been generated.  If not you might need to fix your config of the custom attributes of the task. 

Regards, 
Jocelyn 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Baba Jammi
Sent: Tuesday, 22 November 2011 9:28 AM
To: SAP Workflow Users' Group
Subject: Invalid WDA item link generated from Extended Notifications

I trying to launch WDA item for Leave Request EHP5 thru extended notifications link in outlook email.

SWN_SELSEN does cerate a link in the email as 

"Execute Work Item: Invalid Link (SWN155)". 

Below some information about configuration I have done.

I have maintained WD_HOST as http://---.---.com:1081/sap/bc/webdynpro/ as suggested by earlier posts.

Below workflow configuration has been done in SWFVISU for the Leave Request Approval task.

APPLICATION#HRESS_A_PTARQ_LEAVREQ_APPL
DYNPARAM#LRF_REQUEST_ID=${item.REQUESTID} 

Appreciate if someone can suggest what else configuration I am missing.

Thank you,
Baba Jammi

SAP Workflow Consultant

Aramco Services Company

9009 Westloop S

Houston, TX

-----Inline Attachment Follows----- 

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

-----Inline Attachment Follows-----

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

-----Inline Attachment Follows-----

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

-----Inline Attachment Follows-----

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

-----Inline Attachment Follows-----

_______________________________________________
SAP-WUG mailing list
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/20111129/187d89ac/attachment.htm