Action UrlLauncher after upgrade to 7.4 SP11

Hey folks,

As they say when someone first calls into a radio show...  'Long time listener, first time caller'... and background = I am a workflow developer, not a portal person and not a Basis person either (so be gentle with me?)
Since we upgraded to the portal equivalent of 7.4 SP11, an action that our users used to be able to perform, to Show the PDF of a Shopping Cart in SRM, has failed.

In the past, when the user right-clicked and selected 'ShowPDF' we would launch a URL that specified an ITS Service called ZSRMSCVIEW.  This opened a new headerless window in the browser, and the PDF would be downloaded.

Now when we do the same thing, we get this helpful error message

I can test the service directly from SICF and all is well, it's only from the UWL inbox that it fails. What is puzzling me is the URL generated now... it's really really long and garbled.

Here is the old URL that is generated when the user selects ShowPDF -

https://saplinux62.llan.oursystem.otherstuff:55701/irj/portal?NavigationTarget=ROLES%3A//portal_content/com.sap.pct/every_user/general/iViews/com.sap.netweaver.bc.uwl.iviews/com.sap.netweaver.bc.uwl. uwlURLLaunch &PrevNavTarget=navurl%3A//5f93decd4ce55f610e31e5d760f1d9dd&NavMode=3&CurrentWindowId=WID1466081393791

Not terribly pretty, but certainly functional...

Here is the new URL that is generated (I apologize in advance)

https://saplinuxNN.llan.oursystem.otherstuff/irj/portal?NavigationTarget=ROLES%3A%2F%2Fportal_content%2Fcom.sap.pct%2Fevery_user%2Fgeneral%2FiViews%2Fcom.sap.netweaver.bc.uwl.iviews%2Fcom.sap.netweaver.bc.uwl.uwlURLLaunch&DynamicParameter=forcedURL%3Dhttps%253A%252F%252FsaplinuxNN.llan.oursystem.otherstuff%253A44231%252FHTTPS%253A%252F%252FSAPLINUX31.LLAN.OURSYSTEM.OTHERSTUFF%253A44331%252FSAP%252FBC%252FGUI%252FSAP%252FITS%252FZSRMSCVIEW%252F%2521%253F%257EOKCODE%253DONLI%2526p_objid%253D0010027403%2526ObjectValue%253Da%25253Db%252526sapsrm_botype%25253Dnull%252526sapsrm_boid%25253Dnull%252526System%25253DED1CLNT212%252526sapsrm_wiid%25253D000000929046%252526sapsrm_mode%25253DDISPLAY%252526sapsrm_portalbaseurl%25253D%25253CPortal.BaseURL%25253E%252526sapsrm_pcdlocation%25253D%25253CIView.ID%25253E%2526P_OBJID%253Dnull%2526GuiType%253Dwebgui%2526%257EOKCODE%253DONLI%2526showButtonInPreviewArea%253Dyes%2526ProcessFirstScreen%253Dtrue&forcedURL=https%3A%2F%2FsaplinuxNN.llan.oursystem.otherstuff%3A44231%2FHTTPS%3A%2F%2FSAPLINUX31.LLAN.OURSYSTEM.OTHERSTUFF%3A44331%2FSAP%2FBC%2FGUI%2FSAP%2FITS%2FZSRMSCVIEW%2F!%3F~OKCODE%3DONLI%26p_objid%3D0010027403%26ObjectValue%3Da%253Db%2526sapsrm_botype%253Dnull%2526sapsrm_boid%253Dnull%2526System%253DED1CLNT212%2526sapsrm_wiid%253D000000929046%2526sapsrm_mode%253DDISPLAY%2526sapsrm_portalbaseurl%253D%253CPortal.BaseURL%253E%2526sapsrm_pcdlocation%253D%253CIView.ID%253E%26P_OBJID%3Dnull%26GuiType%3Dwebgui%26~OKCODE%3DONLI%26showButtonInPreviewArea%3Dyes%26ProcessFirstScreen%3Dtrue&PrevNavTarget=navurl%3A%2F%2F5f93decd4ce55f610e31e5d760f1d9dd&NavMode=3&CurrentWindowId=WID1466084252066

I see lots of refences to null parameters, such as SAPSRM_BOID, SAPSRM_BOTYPE - and I know for sure that the XML for this task works correctly for all the other actions.  But here's the XML anyway:

<Action name="ShowPDF" groupAction="" handler="UrlLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="SHOW_HEADERLESS_PORTAL">

<Properties>

<Property name="ObjectValue" value="a=b&amp;sapsrm_botype=${item.BOTYPE}&amp;sapsrm_boid=${item.BOID}&amp;System=${item.systemId}&amp;sapsrm_wiid=${item.externalId}&amp;sapsrm_mode=DISPLAY&amp;sapsrm_portalbaseurl=&lt;Portal.BaseURL&gt;&amp;sapsrm_pcdlocation=&lt;IView.ID&gt;"/>

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

<Property name="GuiType" value="webgui"/>

<Property name="showButtonInPreviewArea" value="yes"/>

<Property name="ProcessFirstScreen" value="true"/>

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

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

<Property name="~OKCODE" value="ONLI"/>

</Properties>

<Descriptions default="Show PDF"/>

</Action>

I don't know what's happened since the upgrade to generate such a humongous URL that is also unable to get the XML parameters of the business object.

Thanks in advance for your patience,
Sue