Hi,
We are implementing the new UI5 landing page for ESS and MSS through the portal, we are on this level.
EHP7 EA-HR 607 / 21
The content is now working but we are having issues with the Approvals lane.
The TASKPROCESSING service has been configured and we have checked the setup as per this discussion to verify UI5 Approval - Missing OData Service TASKPROCESSING
There are currently two issues.
The first issue is that on the landing page the Tasks for apporval are not displayed correctly, we get the Task number rather than the description.
The expanded lane does display the work item descriptions from the backend HR system though.
The second issue occurs when trying to launch the task, for example the leave request approval, SWFVISU has been maintained with the corrcet entry:
When the task is called a webgui screen trys to launch
We need this to hit the webdisplatcher but cannot find a way.
This is the URL being generated when the task is launched
The F12 developer tool displays this error:
[blocked] The page at 'https://gateway
server/sap/bc/gui/sap/its/webgui/?sap-language=EN&~t…ui%20P_WI=000000112002;P_TASK=TS90000018;P_SYS=ECC_TASK;DYNP_OKCODE=OKCODE'
was loaded over HTTPS, but ran insecure content from 'http://HR system server/sap/bc/ui5_ui5/sap/HRMSS_LR_APPR_G/index.html?WI_ID=000000112002&sap-client=450':
this content should also be loaded over HTTPS.
?sap-language=EN&~transaction=*/iwfnd/wf_webgui%20P_WI=000000112002;P_TASK=TS90000018;P_SYS=ECC_TAS…:1
If we modify the below URL taken from the error above to hit the webdispatcher the leave approval screen is displayed.
http://HR
system server/sap/bc/ui5_ui5/sap/HRMSS_LR_APPR_G/index.html?WI_ID=000000112002&sap-client=450?sap-language=EN&~transaction=*/iwfnd/wf_webgui%20P_WI=000000112002;P_TASK=TS90000018;P_SYS=ECC_TAS…:1
The modified URL that loaded was:
https://gateway
server/sap/bc/ui5_ui5/sap/HRMSS_LR_APPR_G/index.html?WI_ID=000000112002&sap-client=450?sap-language=EN&~transaction=*/iwfnd/wf_webgui%20P_WI=000000112002;P_TASK=TS90000018;P_SYS=ECC_TAS…:1
We cannot find where to make this hit the webdispatcher. Implementing this through a central hub gateway has given us continual problems with lack of documentation that we could find on what to configure in the webdispatcher. This is our remaining item now.
Has anyone else had this problem, implemented this functionality using a central hub gateway and webdispatcher or able to help?
Thanks
Jon