My Oracle Support Banner

Common Questions Regarding OSM Worklist (Doc ID 1067854.1)

Last updated on OCTOBER 09, 2019

Applies to:

Oracle Communications Order and Service Management - Version 6.3.1 and later
Information in this document applies to any platform.
***Checked for relevance on 13-Mar-2013***
Review relevance on Sept 04, 2014. This note is still useful
Review relevance on July 06, 2016. This note is still useful


In OSM, end users usually see orders in progress via the worklist. The worklist is part of the OSM Web Client that lists orders which are in the tasks for the workgroup(s) that the logged-in user is associated with.

Since the worklist is one of the most heavily used components of the OSM Web Client, its performance affects usability and ultimately the end user's satisfaction. The performance of the worklist is influenced by a combination of settings that are made by the System Administrator, OSM Administrator, and the user accessing the worklist.

This article intends to make the users aware of the factors that affect memory utilization and system performance when the worklist is accessed so that informed decisions can be made by users when setting up the OSM system.

This article assumes that the reader is familiar with the basic terminology of OSM and has basic awareness of performance tuning for Application Servers and Databases.

Questions and Answers

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Questions and Answers
 What are factors affecting the worklist performance?
 Your documentation does not state that 200 is the preferred value for worklist size. It just says that the possible values are between 200 and 10000. The recommendation (of using 200) is not in line with documentation. Does a change of the worklist size require the performance/stability testing to be performed again?
 Does the worklist affect the memory usage when someone performs a search or when the worklist is displayed? Does the number of concurrent users matter? If we have 5 concurrent users, with worklist 200, is this equivalent in memory usage to 1 user and worklist with 1000 size? If not, which component (users or size of list) matters more?
 If size of worklist causes memory usage to increase, can this be solved by extending available memory? Do you have any algorithm to roughly estimate the dependency?
 What is the recommended worklist size?
 What is the recommended query row retrieved size?
 We need a bigger worklist (bigger than 200 rows). What are the consequences to have it equal to 10000?
 We need a bigger query row retrieved size (bigger than 200 rows). What are the consequences to have it equal to 10000?
 What possible problems may occur if the worklist size is set to 10000?
 What possible problems may occur if the query size is set to 10000?
 Is it possible that worklist size may influence system stability?
 Is it possible that query row retrieved size may influence system stability?
 Is it possible that worklist size may influence system performance?
 What memory should be increased to make it possible to use worklist size and query row retrieved size equal to 10000?
 What are worklist best practices?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.