How to find the tasks a user was able to execute before another user "took" them?

Hi Sean

Thanks for your comments.

I think there is a use case that sits outside the model you describe.

In my case, my process is for recruiting volunteers to a large community project. The project typically has 500 or so volunteers each year working in 20 or so teams. When a volunteer signs up, he/she chooses the teams they'd like to be part of. Some of the larger teams have 2 or 3 team leaders who share the work of approving the volunteers and progressing their application, running security checks, training, having interviews etc.

This is not an "employment" situation, and no-one is going to be reprimanded for not doing a particular task. This is a relationship-based community project staffed and lead by volunteers who mostly have other "real" day-time jobs, and are involved because they are friends of other team members. We have no contracts, no working hours, we PAY to be part of it (we are not paid to be part of it). So "employment law" etc is irrelevant in this case. Most of the "work" will be done by the volunteer team leaders at home in their evenings, and their motivation for doing it is that it means their team will grow quickly. If I make the process too "big-brotherly" then they can simply walk away from it, and they'd be within their rights to do so [it's a little different from most Bonita applications in that regard, I guess]. Bonita needs to be a facilitator, not a police man in my case.

Now the typical use case: If someone volunteers for the team I co-lead and I take/open a task related to that volunteer (eg: get parental consent in the case of a child volunteer), and then I see something in the details that means that one of the other team leaders is better placed to progress that particular application than I am (for example: the person teaches at the same school that they go to or there is some other established relationship - which is far from uncommon), then as it stands, I need to explicitly "unassign" the task from myself in order for the other person to be able to see it. Now -- if we were using the portal, then I am disciplined and would do that, but I guarantee that at least some of the 40 or 50 team leaders will forget that step - AND; we're not using the standard portal. With my replacement front-end, the "take" step is implied when you click on a task, which means it then vanishes from the co-leaders lists - which is why I need this kind of query. My plan would be to mark the task as "taken by Fred", and allow an option to override that. In short I want ALL the leaders of a team to be able to see ALL the pending/active tasks relating to the team - even those that have been "taken" (in Bonita terms) by the other team leaders. Effectively, what I really want to do is turn off the take/assign/unassign logic entirely (it gets in the way, for me) and introduce an alternative locking mechanism for tasks that is aware of when a user opens a form and either abandons or submits it.

I'm working on adding a ProcessAPI call for the query - it's going to be largely the same as the existing logic, but ignores the setting of the "task assigned to" field. At least: that's the theory.

Chris

No need to apologize! I know my use-case is out of the ordinary.
I really appreciate the time you take to understand and answer questions on this forum.

Hi
I did a Summary Page where User had to choose either a Process from a list of Processes or Choose a group from a list and further choose any member from that Group. The result would be to display Pending tasks, Assigned Tasks and completed Tasks.
Take a look at the Below API's

Get task Details based on User id -
../API/bpm/humanTask? p=0&c=100&f=state%3dready&f=assigned_id%3d{{userID}}

List all the Open Tasks -
../API/bpm/humanTask?c=1000&p=0&f=processId={{processid}}&o=state%3dready

List all the Completed tasks -
../API/bpm/archivedHumanTask?p=0&c=100&f=assigned_id%3d{{userID}}

Hope this helps

Hi Dibyajit

Thanks for the feedback, though sadly it doesnt give me what I want. I need a list of tasks that are assigned to OTHER users who are in the actor groups as the logged in user. In other words: the active/pending tasks the logged-in user WOULD have seen if they hadn’t been "taken" by someone else.

In the end, I cracked it by going directly to the tables in the journal DB using SQL queries - but there is no API to get the particular list I need.

Maybe there should be?

Chris