Found a "solution". Created an NONE employee that is used in the initial solution instead of null. This way i know which tasks did not find any solution. Is there a better way?

Several users on the user mailing list have run into this, especially for task assignment use cases. Example use case: @PlanningEntity TaskAssignment assigns a Task to a @PlanningVariable Employee There are so many Tasks, that's better to not assign some Tasks for now. Current workaround: Make a Employee representing NONE, which is the only Employee instance that returns true on employee.isNone() and the score rules are written to deal with that. Technical difficulty to fix: The @PlanningVariable(s) of a @PlanningEntity with planning value null are considered to be "uninitialized". Partial uninitialized solution detection are fundamental for repeated planning (including real-time planning), because the construction heuristics need to detect which parts of the solution to intialize, but not everything because that takes too long.

Regards -- View this message in context: http://drools.46999.n3.nabble.com/Drools-Planner-Simple-problem-having-so... Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users