Invalid WDA item link generated from Extended Notifications

[Dart, Jocelyn]

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://us.mc1117.mail.yahoo.com/mc/compose?to=SAP-WUG@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/20111122/0d61a2cd/attachment.htm