That does make sense. It sounds like I should be adding the facts as domain objects where the index is available instead of generating them during the solution. I was trying to reuse the existing ShiftType3DaysPattern class from the nursing example, but used more than I should have. The code I have is almost working, but it seems to create plateaus. I can give it a "push" by stopping the GUI, making some changes, and then restarting. So I'll add another rule to do that on it's own. I feel like I'm building a kludgy house of cards though.
-- View this message in context: http://drools.46999.n3.nabble.com/Long-pattern-for-Nurse-Rostering-tp4025432p4025452.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
