I think there should be two search pages: one to support process management (processdefinitions and processInstances), one one to support task management (for taskInstances). ProcessInstances: search criteria to include processdefinition, start date, status /state (i.e., active, completed, suspended) TasksInstance: search criteria to include taskname, create date, start date, end date, status / state, processinstance, actorId, pooledActorId Having said this I again raise the concern about performance. Is the database schema and gui architecture able to handle these types of queries when there are 20,000 processInstances and 100,000 taskInstances in the db, and the query results in 2000 hits? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999057#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...