topic Re: Queries from 'start' executionListener on first user task. in Alfresco Archive

Queries from 'start' executionListener on first user task.

jenguran — Fri, 04 Feb 2011 23:58:16 GMT

I have a process that goes:start-> manual task -> user task -> exclusive gateway -> stuff that doesn't matter -> end.I've put a "start" event execution listener on the first user task. The problem I'm having is, the engine doesn't seem to persist anything until some point past that li

Re: Queries from 'start' executionListener on first user task.

frederikherema1 — Sat, 05 Feb 2011 17:28:46 GMT

Hi,

Nothing is persisted until a wait-state is reached (or the end of the process) so in the listeners, nothing will be flushed to the database (transaction won't be committed). It's not possible to use any API methods (eg. query for timers) from inside listener, this will use another transaction an won't see the changes in the DB, which are pending in the uncommitted transaction used by the process execution.

What functionality are you trying to accomplish?

Re: Queries from 'start' executionListener on first user task.

jenguran — Mon, 07 Feb 2011 16:56:56 GMT

Hello, thanks for the reply.

I'm trying to drop a message on our service bus when we enter a user task. The message would have the name of the process, business key, the user task just entered and the last task finished.

Re: Queries from 'start' executionListener on first user task.

frederikherema1 — Wed, 23 Feb 2011 07:16:36 GMT

Maybe you can try the folowing:

When a task is finished, set a execution-variable with the task's ID (or some other stuff that you need) in an taskListener on the task, event=complete (delegateTask.getExection().setVariableLocally()).

When the next task starts, you can use a taskListener, event=start, to send the message you want. Using the passed delegateTask, you can get hold of the variables: delegateTask.getExecution().getVariable('lastFinishedTask'). Info of the current started task is found in the delegateTask itself.

Re: Queries from 'start' executionListener on first user task.

hendrix — Wed, 18 Jun 2014 19:52:14 GMT

Not allowing to query "fresh" data about the process/task trough an executionListener/taskListener seem to limit the usefulness of those…

I have the following scenario:

My ProcessListener is listening to process "end" events to register internally the time and duration of that process instance. I won't be able to do that at the most obvious time: upon process completion. I'm thinking of using that listener only to put the process instance id on some "to be updated" queue so I can later on process what was added to that queue, creating a period of inconsistency on my system.

Re: Queries from 'start' executionListener on first user task.

trademak — Thu, 19 Jun 2014 17:03:08 GMT

An option would be to add an async manual task at the end of your process definition (before the end event) and add an execution listener there. Then all previous data of the process instance is persisted, so you should be able to query anything you are looking for.

Best regards,