[jboss-jira] [JBoss JIRA] Commented: (JBPM-1052) getAllTaskInstances(), getAllProcessInstances()

[Fady Matar (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBPM-1052?page=comments#action_12379504 ] 
            
Fady Matar commented on JBPM-1052:
----------------------------------

Another solution to avoid probable cross-database differences would be to create the hibernate query that would retrieve all the task instances and allow the "super manager" as stated before to view / perform action on them.

Please note that this query might be an over kill when the existing tasks grow large and there has to be a mechanism to allow ordering, grouping and sorting those tasks to reduce the processing time

> getAllTaskInstances(), getAllProcessInstances()
> -----------------------------------------------
>
>                 Key: JBPM-1052
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1052
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2,  jBPM jPDL 3.2.1
>            Reporter: s b
>         Assigned To: Tom Baeyens
>            Priority: Minor
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> Businesses often want a "super manager" to have the ability to see and work on the tasks of all users.  With the current jBPM, it is very difficult to generate a list of all TaskInstances.
> The feature requested is a method for listing all TaskInstances regardless of user.  It appears to be a simple variation on the current methods which request TaskInstances by ActorId or an array of ActorIds.
> One possibility might be to modify the query used by TaskManagementSession.findTaskInstances(String actorId) to use the SQL "LIKE" operator instead of "=" so that the % wildcard could be used to retrieve all TaskInstances.  I don't know if that is portable to all databases; it works well for Oracle.
> It has been suggested that this feature can be created as custom code, but custom code becomes very expensive to maintain and integrate with new releases of jBPM for small development companies like ours.
> A similar feature to retrieve all ProcessInstances regardless of ProcessDefinition would also be highly useful for similar reasons.
> A criticism is that the method would introduce scalability / performance problems.  That is always an issue that is difficult to avoid completely depending on the application.  For example, a business that has thousands of workers all performing the same workflow could generate a very large list using "GraphSession.findProcessInstances(long processDefinitionId)" which would be on the same order as a hypothetical "TaskManagementSession.getAllTaskInstances()" for that particular application.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira