cancel
Showing results for 
Search instead for 
Did you mean: 

Uwl tasks status not get updated in Portal

Former Member
0 Kudos

Hi Experts,

we have implemented ESS/MSS with Universal Worklist and task asiignment works fine, and we are in EP 7.01 and sp08.

Issue is even the tasks process gets completed, the status of the task in UWl is showing as new in MSS overview screen.

Any body would suggest us 'How Task gets updated to complete, when the action is done or process is completed'.

Thanks in advance.

Mahee.

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Issue resolved by uding below function module.

SWLWP_COM_WORKITEM_COMPLETE

Regards,

Mahee.

fabio_sarmento
Contributor
0 Kudos

Hi,

On NW 7.01 you dont have Real Time Refresh, you will have this feature on NW 7.02+ and 7.2+. There are two notes describing the documentation error in NW 7.02 and NW CE 7.20 about functionalities: Real time refresh and Using primary pull to retrieve custom attributes aka "secondary" pull. The note numbers are 1596833 and 1596800. The changes in the documentation will be published on RTC date for NW 7.02 SP9 and NW CE 7.20 SP6. You can use these notes till documentation is published officially.

  • 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

  • You should no longer maintain the snapshot pull period and the value in this field (again a parameter on the portal in the UWL Admin UI for the webflow connector) should be deleted. In other words, it should be left empty as it just creates another temp channel for user which is not required, thus impacting performance.

  • Page refresh rate, (you will find this by going to Personalize View on the main UWL UI), should be increased. UWL user interface will read the data from cache after delta pull has occurred. This way getting the more up to date data retrieved by the last delta pull call. Note that the cache validity period takes precedence. If cache validity has expired then a call to backend will be performed regardless of the fact that delta pull has occurred. So the recommendation is that cache validity should has the longest period value. Then the Page refresh rate should have a decreased-period value. Last, should be the Delta Pull period. In short: Cache Validity > Page refresh rate > Delta Pull. Cache Validity period should be greater than the Page refresh rate which should be greater than the Delta Pull.

*The IView property "Wait duration for UI refresh while waiting for update" can be increased if UI is not responsive. If the value of this property is set to 0 then user interface will be blocked waiting for the call to the backend to complete. In this case after the call is completed and the cache is updated, items are read from cache and displayed in the UI. Assigning a value to this property allows the UI to read the last data found in cache and display it immediately. This way the UI is not blocked while the call to backend is performed in background. Once the time defined in the property expires, the cache should already be updated with the latest items in background, thus the UI showing latest items.

  • GENERAL RULE OF THUMB FOR DELTA PULL AND PERFORMANCE

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)

If there are many workitems then the times should be increased. Increase time to increase performance.

On each logon delta is always fetched. This is why the user may see a change, when logging off from the portal, then logging back on.

I hope it have helped,

Fabio Sarmento

Former Member
0 Kudos

Hi Mahesh,

Uwl tasks status not get updated in Portal in this issue after all the process you setup there is one more property configuration should be done i.e clear cache without doing that uwl task status wont get updated and also look into DeltaPull option(Default Time) in UWLAdministration.

Thanks & Regards,

Brahmarao.

cdc_hr
Member
0 Kudos

Hello,

I have the same problem. Could you please provide me the solution?

Thanks!