On 01-05-14 16:36, jjn wrote:
I was thinking something like this
1. Create a data model for a request in jBPM, where there will be a fields -
2. Create a process model in jBPM for incoming requests being processed by
3. Somehow call optaplanner (??)
Now lets say there are 10 requests
Optaplanner can be used to assign requests to employees (based on the
capability of the employee and the complexity of the request), for eg.
request id 1, request id 3 are done by employee 2.
Sounds like the CloudBalancing
example: instead of processes you have
requests, instead of machines you have employees.
The capacity of the employee should be at least the sum of the demand of
You might also want to add a soft constraints for fairness/load
balancing (see docs section "fairness constraints").
Now in jBPM, I want request 1 and request 3 to be processed by employee
I'd use "immovable planning entities" for that. See this
Basically, you're locking some requests to some employees
and ask OptaPlanner to schedule the rest around that.
Maybe use a decision table -
When there is request 1 and request 3, then assign employee 2 to do a
For decision tables, see my latest 2 video's and the dinner
example in 6.1.0.Beta3.
Decision tables already work in 6.0.1.Final already too (but there's no
View this message in context:
Sent from the Drools: User forum mailing list archive at Nabble.com
rules-users mailing list