topic Re: Prioritization Support in Activiti in Alfresco Archive

Prioritization Support in Activiti

keymaster — Thu, 25 Apr 2013 16:21:02 GMT

Hello.I read in http://forums.activiti.org/content/job-acquisition-filterandhttps://github.com/Activiti/Activiti/wiki/Activiti-configuration-%285.13%29about plans to add prioritization to Activiti. Is it already in the git repository or are there still plans to do it in 5.13?Regards, Wolf

Re: Prioritization Support in Activiti

jbarrez — Tue, 30 Apr 2013 08:23:56 GMT

> about plans to add prioritization to Activiti. Is it already in the git repository or are there still plans to do it in 5.13?

No, not yet planned. It is something which we really like to have, but also difficult to get right.
What do you think would be a good approach? What makes a job more important than other ones? How would you configure it?

Re: Prioritization Support in Activiti

keymaster — Tue, 07 May 2013 11:31:09 GMT

Hello Joram,

we are thinking of a priority given as a parameter to the RuntimeService.startProcessInstanceBy* calls and then giving it to each called SubProcess instance and so on. The prioirty will be store in ACT_RU_EXECUTION. The JobExecuter takes this priority into account.

What do you think?

Regards, Wolf

Re: Prioritization Support in Activiti

jbarrez — Wed, 08 May 2013 14:14:10 GMT

Makes sense, altough you probably can also store it in the process definition (maybe custom extension element) so you don't need to put it in the DB.

Re: Prioritization Support in Activiti

keymaster — Sun, 12 May 2013 08:32:14 GMT

This approach does not match our requirements. We habe different priorized orders using the same process definitions. If we create a pull request after we have a stable solution using jobs and executions, is there a chance to merge this pull request into the main branch?
Regards, Wolf

Re: Prioritization Support in Activiti

frederikherema1 — Mon, 13 May 2013 09:07:08 GMT

Depends on how generic the solution is. Chances are, we'll not be using the suggested implementation. However, if you see it's difficult to plug in your implementation in a vanilla-activiti (not having to change activiti-sources but only configure it using your custom classes) we should make sure it's easier to extend activiti with custom job-handling. The solution you suggest can become part of activiti as an "optional" configuration you can alter in order to use the mechanism suggested by you.