Dear Martin
I hope you are well Image may be NSFW.
Clik here to view.
and many thanks for using the SAP Discussion Forums.
Based upon the scenario that you have described you mentioned wanting to: "automaticly refresh the UWL after the user has closed the window with the SAP GUI HTML".
Ok here there are some important points to highlight and parameters to follow.
With the UWL upon initial logon it firstly takes a total of 5 minutes for all of the tasks to load into the interface and this is completely normal behaviour (on initial logon). The UWL works using two Pull operations. Firstly tasks are pulled from the backend into the UWL cache. and they are then 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. This is upon inital loading as the cache must be built first upon logon so there will always be a delay. Real time refresh in the latest versions, is only when you complete a task.
I would highly recommend reviewing the documentation outlined below:
- SAP KBA number: 1577547 UWL Performance Tips and Considerations
Also, you may want to take a look at our sizing guide that our colleagues colleagues in development support have written in relation to the UWL. You can find the document under this path: www.service.sap.com/sizing> sizing guidelines ' SAP NetWeaver > UWL Sizing guide
These are details that you need in order for the performance to be optimal in the Universal Worklist. Please check through the documentation to see if your parameters are set accordingly and also that you have followed the information in this documentation.
In terms or real-time refresh there is a minimum entry value 20 seconds is the minimum value that the parameter in question can be set to. This is a predefined standard for the "real time refresh" of work items and therefore the value of the paramter must be at least 20.
** Remember RTR (Real-Time-Refresh is ONLY for completed tasks) **
I believe the first point of analysis here would be to examine your current property configurations to see what the current setup is and more importantly does this setup promote and support optimal performance of the Universal Worklist.
In your xml file, find the word refresh. Here you will see it is = 300 by default. This is in seconds, so this means every user will have their page refresh rate set to 5 minutes, unless configured otherwise, through personalization, or xml file.
** Remember never to set any value to a minus number as this will significantly impair performance **
Alternatively the page refresh rate can be configured directly in the xml file for all users. This parameter is displayed as "refresh" = 300 by default. The value is in seconds. (For more information see: Views). The smallest that this value can be set is 1 minute.
So the smallest value you can set this to in the xml file is 60 seconds. Please ensure when you have uploaded your new file, that you rename it, upload it with high priority, then reregister the connector and clear the UWL cache.
** This should be no less that 60 seconds. **
Lastly regarding the core parameter options for the UWL and Refresh setups for tasks being pulled there are a few considerations to bear in mind. The first of which involves the Cache Validity > the page refresh rate > the delta pull channel refresh period. If there is low volume, then these should be low values, if there is high volume, then these should be higher values, but the trade off is items out of date with longer times.
The delta pull period should be no longer than the time that task is required to be updated in the UWL for all new items from the backend. If the items are created more frequently, the period should be shortened and the opposite. Better results for performance will be with greater values, but in this case, the items may not be always up to date. The minimal value is 60 seconds, which is also the default. This corresponds to the following parameter on the portal in the UWL Admin UI for the webflow connector - Delta Pull Channel Refresh Period (in Seconds): 60
Kindly update me as per your findings.
Kind Regards
Troy Cronin - Enterprise Portal Support Engineer