<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Arial, sans-serif" size="2">
<div><font color="#0070C0">This issue is now resolved.</font></div>
<div><font color="#0070C0"> </font></div>
<div><font color="#0070C0">I had changed the Task visualisation XML to:</font></div>
<div><font face="Calibri, sans-serif" size="2" color="#0070C0"> </font></div>
<div><font color="#0070C0">defaultAction="viewPreviewDetaill" from defaultAction="viewDetail" to get the item to launch the user decision in the preview pane only … this then broke the object link. </font></div>
<div><font face="Calibri, sans-serif" size="2" color="#0070C0"> </font></div>
<div><font color="#0070C0">So, for all you people out there excited by launching the Leave Request iView from an object link it is still possible! The looks particularly nice when you are using your own leave Request class with a nice default description such
as ‘Leave Request: Click Here’ rather than Document Database: (GUID).</font></div>
<div><font face="Calibri, sans-serif" size="2" color="#0070C0"> </font></div>
<div><font color="#0070C0">Regards,</font></div>
<div><font color="#0070C0"> </font></div>
<div><font color="#0070C0"> </font></div>
<div><font color="#0070C0">Mark</font></div>
<div><font face="Tahoma, sans-serif" size="2">_____________________________________________<br>
<b>From:</b> Griffiths, Mark <br>
<b>Sent:</b> 20 April 2010 13:46<br>
<b>To:</b> 'SAP-WUG@mit.edu'<br>
<b>Subject:</b> Object visualisation calling Leave Request approval iview</font></div>
<div><font face="Calibri, sans-serif" size="2"> </font></div>
<div><font face="Calibri, sans-serif" size="2"> </font></div>
<div>Hello Wuggers,</div>
<div> </div>
<div>Bit of a tricky question I was hoping someone may be able to help with:</div>
<div> </div>
<div>I am using object visualisation for a Z version of the Leave Request Class to launch the Leave Request Approval iView. I have used this approach at a number of customers, and it was working at my current customer last week.</div>
<div> </div>
<div>The entries I have in SWFVISU are:</div>
<div> </div>
<div>ObjectType: Abap Class</div>
<div>Object Type: Zclass</div>
<div>Method: (no entry)</div>
<div>Visualisation Type: Java WD</div>
<div> </div>
<div>Then for my visualisation I have:</div>
<div> </div>
<div>APPLICATION LeaveRequestApprover</div>
<div>PACKAGE sap.com/ess~lea</div>
<div>SYSTEM_ALIAS SAP_WEBDYNPRO_XSS</div>
<div> </div>
<div>Last week this enabled the object link (NOT THE TASK LINK) in the UWL to call the leave request approver iview . This means I can then use a user decision in the workflow to enable mass approvals, but the user can also access the old screens if they want
to (very nice, you should try it!).</div>
<div> </div>
<div>Obviously I am re-registering and clearing the cache etc.</div>
<div> </div>
<div>Some changes have been made and now when the URL is generated to call the iview it includes: wi_id null. This now creates a ‘500 Internal Server Error’ with a type conversion error for the WI_ID.</div>
<div> </div>
<div>If I remove this WI_ID parameter the iview launches (admittedly without pressing the button next to the relevant item as WI_ID was not passed).</div>
<div> </div>
<div>I can also add in the old style syntax to pass the WI_ID as a DYNPARAM, but in the generated URL this is in addition to the null value, and the null value still creates a ‘Type conversion error’ … if I delete, the iView launches.</div>
<div> </div>
<div>So, any ideas how I can stop the null value from preventing the iView from launching?</div>
<div>Did anyone ever work out where the object visualisation XML is hidden away?</div>
<div> </div>
<div>Any help much appreciated!</div>
<div> </div>
<div>Regards,</div>
<div> </div>
<div> </div>
<div>Mark</div>
<div><font face="Calibri, sans-serif" size="2"> </font></div>
</font>
</body>
</html>