Skip to Content

Starting Release Enhancement Package 5 it is now possible to maintain the refresh option in the transaction POWL_QUERY.

The Personal Object Worklist (POWL) provides the following query refresh options:

FITV_POWL_TRIPS.png

  • On First Page Visit: The query refreshes only when the POWL is initially loaded.
  • On Every Page Visit: The query refreshes each time the POWL is loaded.
  • On First Query Run: The query only refreshes when the query is initially switched on.
  • On Every Query Run: The query refreshes each time the query is switched on.

If no refresh type is set, then the query is refreshed according to the default behavior.

Note: Manual refreshing works in all cases . The setting needs to be maintain seperately for each Query ID.

More information can be found the KBA Article 1806905.

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Lukas Weigelt

    Good to know. This will help us control load on the backend concerning POWL queries better once we upgrade from EHP4 to EHP6. Up until now we did have a “bad feeling” allowing endusers to use the refresh function because of the risk of heavy load, but didn’t see an alternative.

    Thanks for the info, Raynard! 🙂

    (0) 

Leave a Reply