Hi Niladri
No problem at all I am very happy to provide assistance and help out.
The recommendation as per your queries would be to seek consultation from your EP colleagues.
However just some points to highlight. In terms of SSO we would be looking at a wider scope ecapsulating the UWL from the perspective of the Enterprise Portal as opposed to just the UWL Service itself.
In this scenario we are dealing with workitems confined within the UWL.
The UWL itself works using two Pull operations. Firstly tasks are pulled from the backend into the UWL cache and they are pulled a second time from the cache into the UWL User Interface. Due to this
architecture there is an inherent delay in the automatic refreshes of the UWL. There is no way, in the current architecture that the UWL can refresh instantaneously.
So based upon the issue you have described you need to review the underlying concept through which the UWL service operates i.e. the UWL Destination Service Configuration.
Kindly update me as per your findings and follow the points posted in my previous post.
In addition to this kindly review the following documentation:
- SAP Note 1133821 - UWL Destination Service Configuration
Check that after applying Note 1133821 the destination names and the UWL connector names exactly match, even considering case-sensitiveness.If your portal system alias (=UWL connector name) is for example XYZCLNT100, then the rfc destination name should be exactly XYZCLNT100$WebFlowConnector. Please correct the rfc destination accordingly. (If Required)
Kindly update me as per your findings.
Kind Regards
Troy Cronin - Enterprise Portal Support Engineer.