cancel
Showing results for 
Search instead for 
Did you mean: 

How to find all (active and inactive) assigned tasks ?

vire7777
Champ in-the-making
Champ in-the-making
Hi people Smiley Happy

I've seen on the userguide I could find all the tasks assigned to me by the query :
List<Task> tasks = taskService.createTaskQuery().taskCandidateUser("myName").list();

This works well for "active" human tasks but i wanted to know how to find all the tasks assigned to me even if they are not active for the moment. (for example it could help me to know what jobs i would do in the future and whose i have already done in the process)

Thanks for your answers Smiley Wink
4 REPLIES 4

ronald_van_kuij
Champ on-the-rise
Champ on-the-rise
if they are not active for the moment.

What do you meen by this in detail? Not started, ones that you might need to do in the future? Or tasks already done?

chaoyy
Champ in-the-making
Champ in-the-making
I think you wanna get the future task, so you can prepare for these.
In accordance with the theory of the Workflow, you only retrive the created task currentlly, but if you wanna get these, you can parse the process definition xml file manually.

vire7777
Champ in-the-making
Champ in-the-making
In fact i want all the tasks
The ones i have already done, the ones i would do in the future and the tasks i have to do to right now for one process !
So, no other solution than parsing the process xml file ?

Then, how to know all the launched process i m involved in ?
By, first, finding all the lanched process instances, then reading the xml file of each process (because many types of process could be launched) and, finally, check each tasks of them to see if i am the owner…
Not very easy.

ronald_van_kuij
Champ on-the-rise
Champ on-the-rise
Why do you want to know this upfront?

To me it is kind of normal to expect to parse something if I want to know what *might* happen in the future… How do you know which paths would be taken in processes if it is based on steps in the processetc… There is no generic mechanism to know this and therefor not easy…