Setting the "Task count" for views to be "On Demand" does not give good performance
(Doc ID 2454250.1)
Last updated on OCTOBER 25, 2021
Applies to:Oracle Business Process Management Suite - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Fixed in version 18.104.22.168.
In the bpm workspace you can set "Display count of tasks in each view" to "OnDemand" (this is set under Administration, Application preferences).
"On Demand" shows the number of tasks on views that have been visited which should give a performance . So when you first login, all you should see is "My Tasks" count. Then, assuming that a user goes to My Tasks, and clicks edit, and chooses the option to show task counts for views he should see the task count for each view he clicks on.
When a user logs in, they see the task count next to MyTasks and no other views. However, behind the scenes, if you enable the oracle.soa.services.workflow.performance logger, you can see that the workspace actually calls TaskQueryService.countViewTasks for each view, which causes a significant performance delay.
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